To-do Application by Hilag Shah | DEMO
- Tasks should be displayed in a Tabular format, using the Ant Pro table component.
- Table should have timestamp(auto set and uneditable).
- Table should have title(Mandatory Field with create and update, maxlength=100)
- Table should have description(Mandatory Field with create and update,maxlength=1000)
- Table should have due_date(Optional Field with create and update,date should not be greater than the current timestamp)
- Table should have tags(Optional Field with create and update,multiple tags with same name should appear once)
- Table should have tags(Optional Field with create and update,multiple tags with same name should appear once)
- Table should have status(Optional Field with create and update,four status - OPEN,WORKING,DONE,OVERDUE)
- Table should support pagination
- User should be able to ADD,MODIFY,DELETE,FILTER,SORT the data
- Case insensitive search of tasks
- Mock API Data(need to follow step 1 i.e. "npm run mock api" to see data)
- Deploy Application and add comments to code
Note: I did not have a VISA credit card/debit card and thus failed to deploy on AWS,GCP or Azure.Thus I have deployed the application on Netlify.
In the project directory, you can run:
This will install all the dependencies in node_modules folder
Runs the mock-api to feed data into our todo application.
The API will by default run on PORT 3001 http://localhost:3001 from where we fetch the JSON data and feed it into out ant-pro table.
Open a new console on completion and keep the current console running.
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.This is basically because of some configuration issues while using ant-pro tables.
Launches the test runner in the interactive watch mode.
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.
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.