Getting Started with Wanikani Navigator

• Add a .env file to root containing the key REACT_APP_API_KEY. Copy in the key from your Wanikani account (if interviewer, I'll send the file).
• Run yarn to get relevant packages.

Developer Comments

• Managing network delays and async calls:
  • Would likely have had a dedicated state that handles network status.
  • For instance, upon filter submission I would set the network state to “loading” and use that to indicate to the user something’s loading in the background.
  • Upon success/failure of API call, I’d update the state accordingly. On failure there would be some error message asking the user to try again or some issue was found.
  • If the app were much larger, I’d make use of redux toolkit and take advantage of default middleware like redux-thunk for handling calls.
• API key would definitely not have been used in the client side for security reasons. Normally, would call upon backend from which I'd receive tokens that I can use to authorize calls to retrieve only the data I need to display.

Available Scripts

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn cypress

Be sure to yarn start before running this for this basic E2E test.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
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.

yarn 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.