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

[BUG] Replace legacy query.filter_by call

Abierto
#166 0 comentarios 0 reacciones 1 asignado Reclamado por @crossmant1 Ver en GitHub
bug
Lenguaje dominante
Python
Estrellas
7
Forks
2
Merge medio
4 d 23 h
PR fusionados (30 d)
2

Descripción

## Location of the Bug
* **File/Feature:** ```admin.py```, ```api.py```, ```auth.py```, ```main.py```, ```mfa.py```, ```polls.py```, ```test_admin.py```, ```test_auth.py```, ```test_main.py```, ```test_mfa.py```
* **Version:** ```v1.9```

## Description of the Bug
The code uses legacy calls that have been replaced by newer ones. Notably, query.filter_by() is extensively used throughout the code base. Perform research, investigate, and deploy a solution. Additionally, look for any other legacy calls in the code and replace those as well.

## Intended Functionality
Keep all functionality of the application the same.

---

## Acceptance Criteria & Solution Requirements
*To close this issue, the following must be met:*
- [ ] 1. Application runs as expected (bug is resolved without breaking existing features).
- [ ] 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. Any other requirements that are specific to this issue

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

The issue lists ten files (admin.py, api.py, auth.py, main.py, mfa.py, polls.py, and their test files) where query.filter_by() calls need replacement. First, examine the SQLAlchemy usage in these files to understand the current patterns. Run existing tests to ensure functionality remains unchanged after replacements. Look for other legacy SQLAlchemy calls as instructed.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
python
Área
backend, database
Tipo de issue
Refactorización
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
55/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.