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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is an entry/discussion point for a suggestion which follows the first example on the react file structure page, but with more specificity, catered to what we are actually building. This ruleset prioritizes speed of development and context understanding over component conformity & isolation.
The general rules:
Our react front-end's job is to visually draw stuff on a web page. As a result, the file structure should match the structure of the visual behavior of our application.
Be explicit about which components can be shared outside of their domain/page and which can't (common folders exist on all domain levels).
Use your best judgement when you should/shouldn't extract things. We're all grown ups and we're all rowing in the same direction. We have designs and we'll have good guesses about what will be reused and what won't.
We have a convention on words which indicate a page's primary function - maybe this looks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Used to supply the client w/ AR model validation rules
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters