Why browse for cat images elsewhere when you can use Cat Viewer?
- Previous button should not be displayed when the user is on the first image
- Next button will always be active, but will either display the stored image if present, or fetch a new image if the user is already on the last image fetched
- If there's an error hitting the api, the current cat will remain displayed. For future work, we would want to notify the user
- The UI will indicate loading to the user when waiting for an api call to complete. While waiting for a response, the user will be unable to generate a new request, but would be able to navigate to previous or next cats if they were already loaded in the app
- There will be a get random cat button which will fetch a new cat, and take the user to very end.
- Clicking previous after getting a random cat will take the user to the second to last cat fetched, rather than the second to last cat viewed (otherwise the user would be unable to navigate to certain images without additional features)
- Storing the image was interpreted as storing the url link to that image
- Most of the breed and category information would be irrelevant to our users. As such, it was not displayed
- In the project directory, run
npm install npm start- The app should load on localhost:3000
- Shoring up UI after speaking with a designer
- Organizing code for ease of maintenance and new feature developer
- Expanding test coverage & moving away from render due to deprecation warning
- Error handling
- CSS