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
Comments
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? |
Yeah, you are right, i got some problems with my ideal |
…/add-yjoer docs: add yjoer as a contributor
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'?
The text was updated successfully, but these errors were encountered: