| Commit message (Collapse) | Author |
|
Group globals and data classes near module imports, keep primary classes
and functions together, and move implementation helpers after their
public callers.
Reorder Alembic setup so configuration happens after the required
helpers are defined, without changing runtime behavior.
|
|
Rename configuration keys, task helpers, forms, network utilities, and
view endpoints to make their responsibilities and domains more explicit.
Align source-management routes and templates with the new terminology
and rename the target-matching module and related task abstractions
consistently.
BREAKING CHANGE: configuration keys have been renamed and sent-source
routes move from `/sent` to `/sources`, with corresponding blueprint
endpoint changes.
|
|
Expand function and method documentation with consistent reST parameter,
return, and exception fields while clarifying behavior where additional
context is useful.
Normalize test and migration docstrings to the same documentation
conventions.
|
|
Rely on the database uniqueness constraint and existing `IntegrityError`
handling instead of performing a redundant pre-insert user lookup.
|
|
Rename shared Flask extension singletons to conventional lowercase names
and update imports throughout the application and tests to remove
redundant aliases.
|
|
Expand Ruff checks for bugbear, complexity, pathlib, return statements,
simplifications, upgrades, and docstring style.
Apply the resulting behavior-neutral cleanup across application and test
code.
|
|
Break up monolithic views, task helpers, networking, CLI, and
application extension setup so each module owns a focused concern.
Reorganize the test suite around the new boundaries while preserving
existing Webmention behavior and coverage.
|
|
Require persistent non-placeholder signing keys outside local
development and bind login sessions to the current password hash so
password changes revoke existing cookies.
Enforce a minimal password policy for user administration while
preserving long Unicode passphrases without arbitrary composition
limits.
|
|
|
|
Make database initialization and upgrades explicit so new installations
cannot silently modify an existing or unversioned schema.
Keep Flask-Migrate commands available separately and package the
migration environment with the application for reliable deployment.
|
|
Add commands to list users, reset passwords, and delete accounts.
Move mail and user commands into dedicated CLI modules.
|