daftmonk / angular-project-draft Goto Github PK

We want at least the client/app/routes and client/app/components folders, but theres arguments against having services and filters folders.

It's hard to think of filters and services as components by themselves. They're globally available across the app, and might be used across many different components. And in large apps you may have a very large number of services and filters that would bloat the components folder and make it hard to find things.

The services and filters folders would be used for services and filters that are used across the app, not just by a specific component. Component folders could contain services and filters specific to that component.

The alternative would be to put services and filters inside category folders inside of components. For example:

components/apiRepository/user.service.js
components/apiRepository/item.service.js
components/nameFilters/name.filter.js
components/dateFilters/user-age.filter.js
components/dateFilters/time-posted.filter.js

Thoughts on which method would be preferred?

I'm uneasy about the word "public" as a directory name. It seems to imply that whatever is not contained in it is "private" - either requiring authentication or remaining on the server side. If there's a "public" directory, I expect there to be a "private" directory next to it, but there isn't. Also, a lot of people use the word "public" in place of "client" and in contrast to a directory named "server". So that's confusing too.

"public" as a directory name just seems like a relic from the past when an app server rendered things server side and static things were handled by a separate server. To me, the word "public" doesn't distinguish clearly what should go here from what should not.