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
{{ message }}
This repository has been archived by the owner on Mar 9, 2021. It is now read-only.
Any plans on supporting subfolders within the generators? Specifically, I am creating many small components all for one screen, while having several screens in my app. In the end I will probably have 30-40 components in my app, mainly to keep logic, styling, JSX, and testing more modularly. Specifically I'm using StorybookUI to refine my component designs/testing.
The App/Components folder is getting pretty cluttered and if I could run something like ignite g component Product/Review to generate App/Components/Product/Review.js (instead of App/Components/ProductReview.js), it would help with organization. The respective stylesheet would have to be put into the same respective subfolder under App/Components/Product/Styles/Review.js
The text was updated successfully, but these errors were encountered:
Any plans on supporting subfolders within the generators? Specifically, I am creating many small components all for one screen, while having several screens in my app. In the end I will probably have 30-40 components in my app, mainly to keep logic, styling, JSX, and testing more modularly. Specifically I'm using StorybookUI to refine my component designs/testing.
The App/Components folder is getting pretty cluttered and if I could run something like
ignite g component Product/Review
to generate App/Components/Product/Review.js (instead of App/Components/ProductReview.js), it would help with organization. The respective stylesheet would have to be put into the same respective subfolder under App/Components/Product/Styles/Review.jsThe text was updated successfully, but these errors were encountered: