acm-udayton / acm-udayton/ACM-Meeting-Records

[FEATURE] Create RESTful /api/v1 endpoints for application

Ouverte
#162 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
backend enhancement
Langage dominant
Python
Étoiles
7
Forks
2
Merge moyen
4 j 23 h
PR mergées (30 j)
2

Description

## Feature Description

Create new blueprints for /api/v1 endpoints that mirror the existing endpoints in the existing non-API application.

Use pydantic for request and response schema and also be sure to use `app.register_api_blueprint()` to register these blueprints so that Swagger UI (#161) can document the API automatically.

All business logic should come from existing services or be placed in new services, as per #160.

## Why It's Worth Implementing

This is key to being able to decouple the frontend from the backend in `v2.0`.

---

## Acceptance Criteria & Solution Requirements
*To close this issue, the following must be met (can be finalized in the comments):*
- [ ] 1. Application runs as expected with the new feature integrated seamlessly.
- [ ] 2. Code quality metrics are maintained, and linting has been considered in development.
- [ ] 3. Testing metrics are maintained, and tests have been updated/added wherever relevant during development.
- [ ] 4. Documentation has been updated to reflect the changes made during development.
- [ ] 5. All application functionality can now be accessed from the new RESTful API.
- [ ] 6. Use services (#160) for all business logic.
- [ ] 7. JWT authentication has been implemented (#154)

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.