✨[Feature] Agree on a file naming scheme
Closed this issue · 3 comments
Is your feature request related to a problem? Please describe.
Currently we are naming our files using both camelCase and kebab-case.
Describe the solution you would like
We need to agree on one naming convention and stick to it.
Additional context
We'll rename the files when we have finished the MVP API on the backend and moved towards the frontend. This'll be done as to minimize merge conflicts.
Issue-Label Bot is automatically applying the label enhancement to this issue, with a confidence of 0.93. Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
I think upper CamelCase names for files exporting a constructor and either always lower camelCase or always kebab-case names for function files would be fine. Besides, kebab-case is mandatory for NPM packages, so if we wanted to refactor some modules into independent packages they would have to be renamed in kebab-case.
This issue has been inactive for a while. Adding the Stale label. 😕