AP / Java key parts
- Class definition for Database (OOP) - Definitions of Employees and Companies
- JPA CRUD operations - CRUD operations works for companies
- API requests and response - Requests to employees and companies API
Show coding parts
- Input (Input validation, multiple paths of code) - Login validates usernames
- Output (HTML generation) - Generates a
div for each individual user, liquid takes each company and creates and object for each person
- Format/Visualization (SASS generated CSS) - SASS generates CSS on the frontend
- Data/Array/JSON management - Management with DTO, allows us to bypass the entity, response body converts java to JSON
- Multiple endpoints Get/Post/Put/Delete (alternate paths for code) - CRUD up to date for Employees and Companies
- Database initialization - Initialization of the Employees and the companies
- SQL visualization - Companies and users admin panel
Long Term Plan
Our long term plan is to take and improve upon our company-employee response and then integrate that fully into our frontend. So far, we need to ensure the sorting methods works with their respective repositories, and then we can move fully into getting them to work with our frontend.
Key Features (for this live review)
- Basic outline of the frontend
- Admin panel displaying ocmpanies
- Admin panel displaying employees
- PATs
Individual Review Tickets
AP / Java key parts
Show coding parts
divfor each individual user, liquid takes each company and creates and object for each personLong Term Plan
Our long term plan is to take and improve upon our company-employee response and then integrate that fully into our frontend. So far, we need to ensure the sorting methods works with their respective repositories, and then we can move fully into getting them to work with our frontend.
Key Features (for this live review)
Individual Review Tickets