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
I'd like to see a documents subdirectory for ui/components, containers & pages in the same way the api has a documents subdirectory. When I create a new project with Base and starting making new collections and related UI components, I create a subdirectory for each new collection under both api and the ui directories.
The text was updated successfully, but these errors were encountered:
Had a quick look. I like it but Ryan might not merge the PRs. The current structure is very clear for beginners whereas the new one could make less sense.what do you think Ryan ?
Hi @rgstephens@arthurkirsz. Agree with Arthur here. I do prefer this more personally, but I want to keep things as close to the Meteor Guide/simple as possible. Something like an extra directory may seem like a silly thing to split hairs over, but—especially for beginners—it introduces the added question of "do I have to do it this way?"
Going to think about this and flag it as a consideration for Base 5.0. Thanks for submitting this, Greg :)
I'd like to see a documents subdirectory for ui/components, containers & pages in the same way the api has a documents subdirectory. When I create a new project with Base and starting making new collections and related UI components, I create a subdirectory for each new collection under both api and the ui directories.
The text was updated successfully, but these errors were encountered: