REACT TECHNICAL TEST A Command Shift project to simulate a technical test during the recruitment process. A timescale of 5 days was suggested and in this time I had a working MVP, I did not complete this project with TDD methodolgy and need to add tests. I have since added styling and refactored.
Technologies Used This project formed part of the frontend module and required CSS, API but with a focus on consolidating React skills.
- React
- Axios
- CSS
Further Features
- Auto complete on search-bar
- Testing
- Cursor to change to magnifying glass on hover
- Lightbox added for bigger view of, ability to zoom in on and navigate between images
Installation instructions
A section demonstrating that you met the requirements
Future Features To Develop
- Limiting number of results displayed and adding an option to retrive more.
- Ability to select an image and enlarge it.
- Search bar autocomplete.
- Clearer messaging if not results.
- Testing
A section demonstrating that you met the requirements
If there are bonuses, a section demonstrating that you met them
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may 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.
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.
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.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify