Below is a brief overview of my design & implementation strategy
I separated state & handlers concerns from presentational ones according to best practices. This to increase modularity making it easy to integrate this component. I also integrated TypeScript to provide granular type-checking and avoid runtime bugs. I also added logic to cancel pending Ajax promises when component gets unmounted. This will help avoid memory leaks.
Here I intentionally only used React to manage form state per best practices. I also added localStorage support to cache form state on submit as requested. The submit handler is modular giving us the option to swap out axios for apollo to speak to a GraphQL backend.
- I used Styled Components as requested in order to keep style rules modular. I implemented the necessary config to SC wired up with TypeScript and also investigated workaround the a bug in the SC type definitions in the latest version.
- Grid layout powered by Flexbox. Keeps styling easy to reason about
- You'l notice I wrapped control groups in
<div role="group>elements instead of
<fieldset>. [There's known bug that}(https://stackoverflow.com/a/28078860) that makes
display: flexnot work on
<legend>s. Setting the role should help assistive devices understand the grouping
I'm very please to report that overall test coverage is around %85, my strategy to isolated structural (smoke) tests from behavior-driven ones will allow the test suite to evolve independently along both paths. Testing strategy has full async support for backend data fetch & posts.
In the project directory, you can run:
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you
eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can
eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except
eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use
eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.