Underlay Registry #1
npm install
npm start
Navigate to localhost:9876
To build and test components, we use Storybook. To run:
npm run storybook
Navigate to localhost:9001
npm run prod
Navigate to localhost:9876
The client side code follows a Container/Component split, as is common in React-based sites. The structure and difference between the two in this repo is not exactly as described in the preceeding article. For this repo, the following describes how containers and components are differentiated:
- Associated with a specific URL route
- Only a single container is used on a given URL route
- Calls hydrateWrapper() to initialize React bindings after using server-side renered HTML for immediate display.
- Holds the ground truth data for a given view. Often the ground truth data is passed into containers as props through hydrateWrapper(), but in cases where the ground truth data is being changed, the container will hold ground truth data in it's state.
- All other non-container components :)
- Many components are used within a given URL route
- Can store its own state if needed for UX functionality - but should always update the ground truth data held in its parent container.
- Can make its own API requests when the functionality and layout of the pertaining request is contained within the single component. Though if this request influences the ground truth data, the component should be passed an updating function that allows it to update the ground truth data held in the container.
Preferred practice is to prefix commits with one of the following categories:
fix: for commits focused on specific bug fixesfeature: for commits that introduce a new featureupdate: for commits that improve an existing featuredev: for commits that focus solely on documentation, refactoring code, or developer experience updates
