- Create a new collection with the following fields: a. Name of the collection b. Description c. Images in the collection
- After the Creation of the collection, the user should be redirected to the dashboard listing the new collection created.
- On click of the collection, you should be redirected to the route of that specific collection where you can view the content with the specified fields.
- You should be able to edit the collection.
- You can delete the collection that you create.
- Make sure that while creating your collection, fields should not remain empty i.e., there should be form validation in it with an appropriate message.
React Redux should be used for state management
-
Landing page
-
User can then add a collection by clicking on the Add Collection button. An error is shown if any of the 3 fields are left empty
-
User is then redirected to view collections page which shows the current collection created.
-
User can edit the name of collection, description of collection and can also add new images. An error message is shown if the user leaves name or description field empty
-
The user can delete any image they want. If they try to delete the last image, an error message is shown.
-
The user can delete any of the collections they have created. If the last collection is deleted, the user is redirected to the landing page with the view collections button disabled
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