You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: [example] There is a discrepancy in our file naming on backends in regards to using camelCase or kebab-case.
Product: [example] We want to implement an Eslint rule that checks whether the file names are all kebab-case, and add it to our backend template
Reasoning: [example] kebab-case is the go-to standard for Node.js development and eslint automates enforcement of the standard, such that no onboarding is needed
Problem: [example] There is a discrepancy in our file naming on backends in regards to using camelCase or kebab-case.
Product: [example] We want to implement an Eslint rule that checks whether the file names are all kebab-case, and add it to our backend template
Reasoning: [example] kebab-case is the go-to standard for Node.js development and eslint automates enforcement of the standard, such that no onboarding is needed
Additional details: [example] There seems to be a rule online for this: https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/filename-case.md
Also, please note that React component files are to be named in PascalCase as per React standards.
The text was updated successfully, but these errors were encountered: