Peter Stockings 6095e76f10 Here is a conventional commit message summarizing the refactoring work:
```
feat: Refactor calendar feature into blueprint

- Moved calendar logic from `features/calendar.py` and `app.py` into a new blueprint at `routes/calendar.py`.
- Removed the `Calendar` class and refactored logic into helper functions within the blueprint module for better organization and readability.
- Eliminated the `pandas` dependency for date range generation, using standard `datetime` operations instead.
- Resolved circular import issues between `db.py`, `extensions.py`, and `routes/calendar.py` by adjusting import locations.
- Corrected `url_for` calls in templates (`calendar.html`, `partials/people_link.html`) to reference the new blueprint endpoint (`calendar.get_calendar`).
- Fixed an `AttributeError` related to HTMX request checking in the calendar route.
- Corrected `AttributeError` related to `.date()` calls on `datetime.date` objects in view processing functions.
- Updated `templates/changelog/changelog.html` to document the refactoring and associated fixes.
```
2025-03-30 22:20:48 +11:00
2025-02-01 21:26:52 +11:00
2022-07-15 21:06:27 +10:00
2022-09-17 16:42:50 +10:00
2022-09-10 15:09:17 +10:00
2022-09-17 13:38:41 +10:00

Workout tracker

Track topsets over time.

Setup

Install python>3

Install dependencies

$ pip install -r requirements.txt

Enable development mode

PS $ENV:FLASK_ENV='development'

Set database url, either setup postgres database locally use migration script or expose deployed one

$Env:DATABASE_URL = 'postgres://postgres:***@***:***/***'

Start application:

flask run

Features

  • Track topsets for each workout
  • Multi user
  • Authentication/Authorisation
Description
No description provided
Readme 4 MiB
Languages
HTML 43.9%
Python 35.5%
Jupyter Notebook 18.8%
PLpgSQL 1.2%
CSS 0.6%