Projekat na ovom repozitorijumu predstavlja admin deo nase aplikacije. Sam administratorski deo sluzi za unos novih statistika na mesecnom nivou, pozeljno par dana pred kraj meseca, kako bi statistika bila sto verodostojnija. Admin je lice sa posebnim ovlascenjem, ne postoji nikakv tip registracije jer se ovlascenja dobijaju od strane nadleznih koji admin podatke (email i password) direktno unose u bazu i daju adminu na koriscenje. LoginPage.js fajl predstavlja stranicu na kojoj je moguce uneti dobijeni email i password. U slucaju uspesnog logovanja admin biva prosledjen na dashboard. Ukoliko je pri logovanju pogresio sifru, bacend vraca gresku 422 i admin se o tome obavestava alert-om. Ukoliko je pri logovanju pogresen email ili zapravo takav ne postoji, backend vraca gresku 404 i admin se o tome obavestava alert-om. U slucaju korektnog logovanja, admin je prosledjen na dashboard. Na dashboardu se nalaze 3 forme, za unos nove statistike, za unos novog drveta i njegove statistike i za uklanjanje drveta iz baze. Ove forme nalaze se u Forms.js fajlu. Funkcije za logovanje admina rade sa AuthService.js fajlom, a funkcije za izmenu baze sa SumeService.js fajlom. Oba service fajla nalaze se u folderu services. Koriscenjem axios.get i axios.post metoda, vrsi se komunikacija sa backednom.
Za svako unosenje podataka o statistici pamti se mesec i godina za koju su ti podaci uneti. Odnosno na osnovu trenutnog datuma se podaci uzimaju. Na klijentskoj strani aplikacije vidljivi su podaci koji su uneti prosle godine. To znaci da svi podaci koji se sada unesu su trenutno vidljivi samo u bazi, a ne na klijentskoj aplikaciji. Klijent ce moci da ih vidi tek pocetkom sledece godine. Za potrebe testiranja unosa novih podataka moguce je u api delu promeniti da se prikazuju podaci za ovu godinu. Vise o tome u README.md na sume-srbije-api. Admin aplikacija se pokrece na http://localhost:3000.
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 the browser.
The page will reload if you make edits.
You will 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