Peter Stockings a8fe28339b I have refactored the SQL Explorer functionality into its own blueprint (routes/sql_explorer.py) with a /sql URL prefix. This involved moving the relevant routes from app.py, registering the new blueprint, removing the old routes, updating url_for calls in the templates, and documenting the change in the changelog. ...

Here is a conventional commit message summarizing the changes:

```
feat: Refactor SQL Explorer into blueprint

- Moved SQL Explorer routes (view explorer, save/load/execute/delete queries, view schema, plot queries) from `app.py` into a new blueprint at `routes/sql_explorer.py`.
- Added `/sql` URL prefix to the blueprint.
- Registered the new `sql_explorer_bp` blueprint in `app.py`.
- Removed the original SQL Explorer route definitions from `app.py`.
- Updated `url_for` calls in relevant templates (`sql_explorer.html`, `partials/sql_explorer/sql_query.html`, `base.html`) to reference the new blueprint endpoints (e.g., `sql_explorer.sql_explorer`).
- Updated `templates/changelog/changelog.html` to document this refactoring.
```

2025-03-31 23:00:54 +11:00

..

auth.py

Here is a conventional commit message summarizing the refactoring work:

2025-03-30 22:20:48 +11:00

calendar.py

feat: Refactor notes functionality into blueprint

2025-03-31 22:08:47 +11:00

changelog.py

feat: Add static changelog page

2025-03-30 21:30:25 +11:00

notes.py

feat: Refactor notes functionality into blueprint

2025-03-31 22:08:47 +11:00

sql_explorer.py

I have refactored the SQL Explorer functionality into its own blueprint (routes/sql_explorer.py) with a /sql URL prefix. This involved moving the relevant routes from app.py, registering the new blueprint, removing the old routes, updating url_for calls in the templates, and documenting the change in the changelog.

2025-03-31 23:00:54 +11:00

workout.py

feat: Refactor workout functionality into blueprint

2025-03-31 22:38:48 +11:00