Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Component prefix #78

Closed
mooo-ooo opened this issue Nov 16, 2017 · 3 comments
Closed

Component prefix #78

mooo-ooo opened this issue Nov 16, 2017 · 3 comments
Assignees

Comments

@mooo-ooo
Copy link

mooo-ooo commented Nov 16, 2017

Do we really need to use specific component's name as a prefix, for example: ' user/userAPI', is that essential? could we use ' user/API'?

@goldbergyoni goldbergyoni self-assigned this Nov 19, 2017
@goldbergyoni
Copy link
Owner

It's a matter of style and there's probably no clear cut here but I personally suggest using the fully contextual object name, userService, because it's sometimes accessible not via file system. For example, when navigating through the code and arriving some code, the class name "API" won't tell you much and switching to file system view is not always convenient. The same can be said about generating memory dump or code coverage reports - all you have is the class/object name, not its parent folder name.

Makes sense?

@mooo-ooo
Copy link
Author

Yeah, you are right, i got some problems with my ideal

MatanYadaev pushed a commit to MatanYadaev/nodebestpractices that referenced this issue Aug 16, 2023
…/add-yjoer

docs: add yjoer as a contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants