| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
Centralize SQL row counts, hostname parsing, and content-type
normalization so tasks, forms, and scanners share consistent
implementations.
Simplify periodic task registration and admin lookups with table-driven
setup and Flask-SQLAlchemy's built-in 404 helper.
|
| |
|
|
|
| |
Use shared Unicode category validation so passwords reject C1 controls
in addition to C0 and DEL, and reuse the same helper for URL validation.
|
| |
|
|
|
|
|
|
|
| |
Replace overlapping WTForms URL and regex checks with a single `HTTPURL`
validator that enforces parseable HTTP(S) URLs without rewriting
whitespace.
Add coverage for malformed hosts and ports plus case-insensitive
schemes.
|
| |
|
|
|
|
| |
Remove the generic cross-field equality validator and keep the
source-versus-target check directly on `EndpointForm`, where the
validation rule is actually used.
|
| |
|
|
|
|
|
|
| |
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.
|