How mckenz-e/project01 works
This is a browser-based asset inventory and borrowing application. Users register or log in, browse available assets, borrow them, and return assets assigned to them; administrators can add, edit, and delete inventory, while the history screen reports asset/user/status information and exports a PDF. The frontend pages call an Express API, which queries MySQL. The README gives no further feature detail, so this map follows the sampled handlers and page scripts; some page files are present in the tree but their implementation was not sampled.
Main entry points: index.js Express API · manage.js Manage inventory · history.js Asset history · login.js Login
Components 13
Browser workflows
- Login
Frontend/login.js - Registration
Frontend/register.js - Asset catalog
Frontend/main.js - Borrow assets
Frontend/borrow.js - Return assets
Frontend/return.js - Add inventory
Frontend/admin.js - Manage inventory
Frontend/manage.js - Edit inventory
Frontend/edit.js - Asset history
Frontend/history.js
API and persistence
- Express API
Backend/index.js - MySQL database
Other components
- User
- PDF exporter
Connections 20
- User → Login: uses
- User → Registration: registers
- User → Asset catalog: browses
- User → Borrow assets: borrows
- User → Return assets: returns
- User → Add inventory: adds assets
- User → Manage inventory: manages
- User → Asset history: views history
- Login → Express API: POST /login
- Registration → Express API: POST /register
- Asset catalog → Express API: GET /main
- Borrow assets → Express API: GET /borrow; PUT /assets/:id
- Return assets → Express API: GET /return; PUT /return/:id
- Add inventory → Express API: POST /assets
- Manage inventory → Express API: GET /main; DELETE /assets/:id
- Manage inventory → Edit inventory: opens edit
- Edit inventory → Express API: GET /assets/:id; PUT /edit/:id
- Asset history → Express API: GET /information
- Asset history → PDF exporter: exports report
- Express API → MySQL database: queries and updates