Our API is an API that allows users to create recipes, ingredients, and meal plans. A user can use premade recipes or ingredients and add ingredients to their recipes. A user can make user specific weekly meal plans with meal plan entries that have recipes in them.
Issues
Pull Requests
Worked on
- Project setup: Created the Spring Boot skeleton and wrote the OpenAPI (api.yaml) contract
- DevOps: Added a Dockerfile, docker-compose for local dev, and GitHub Actions CI
- Quality gates: Required 70% service-layer test coverage with JaCoCo and set up auto reviewers
- Deployment: Published the Docker image to GHCR on merge to main
- Meal Plan API: Built CRUD routes for meal plans and their entries, plus Swagger UI docs
Issues
Pull Requests
Worked on
- Built the the User, Ingredient, and Recipe entities
- Including tables, constraints, and relationships in neon
- Ingredient API has pagination browsing, duplicate name validation, and service tests
- Developed Recipe API functionality, pagination, sorting, ingredient association, ownership checks, and HTTP responses
Issues
Issues on App Repo
Pull Requests
Pull Requests on App Repo
Worked on
- Built the Android App interface
- Created the login and sign up screens
- Designed the home screen and navigation menu
- Added the Recipe Screens
- Added Google OAuth to both the Back end and the Android App
Issues
Pull Requests
Worked on
- Helped set up the online database
- Built the Meal Plan and Meal Plan Entry database entities
- Worked on the User GET, PATCH, and DELETE API endpoints
- Started the work on the API Springboot security and error handling.
Pull the repo into Intellij or a similar IDE, then go into the terminal and ensure you are in the api directory.
Then run ./gradlew build