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

[TASK] Migrate business logic to services

Ouverte
#160 0 commentaires 0 réactions 2 personnes assignées Réclamée par @ethanlally Voir sur GitHub
enhancement
Langage dominant
Python
Étoiles
7
Forks
2
Merge moyen
4 j 23 h
PR mergées (30 j)
2

Description

## Feature Description

Business logic should be moved from within the routes and blueprints to separate services. These services should be contained in a `app/services` directory, with files mirroring the blueprints where they would have previously been located.

## Why It's Worth Implementing

Not only does this make our app more consistent with best practices and increase maintainability and testing ease, it also is key to our process of decoupling the frontend and backend. These services will allow us to keep consistent business logic during the intermediate phase where we keep the existing Jinja template serving and also build out the RESTful API.

---

## Acceptance Criteria & Solution Requirements
*To close this issue, the following must be met (can be finalized in the comments):*
- [x] 1. Application runs as expected with the new feature integrated seamlessly.
- [x] 2. Code quality metrics are maintained, and linting has been considered in development.
- [x] 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 business logic has been removed from the `app/blueprints` directory, and is instead kept in the `app/services` directory.

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.