bvandeusen/FabledScribe
1
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 53 Wiki Activity

Two milestones: a note can carry its own check (317), and a rule keeps what it used to say (323) #135

Merged
bvandeusen merged 23 commits from dev into main 2026-08-31 00:01:15 -04:00
Conversation 0 Commits 23 Files Changed 78
+6 -2
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit b134fe9aa1 - Show all commits
tests/test_services_backup.py
+6 -2
View File
@@ -242,9 +242,13 @@ def test_the_column_guard_covers_every_table_with_a_row_helper():
with a new helper, and not to the registry, would be unguarded and look with a new helper, and not to the registry, would be unguarded and look
guarded. Join tables have no model class and carry both their columns by guarded. Join tables have no model class and carry both their columns by
construction, so they are the only permitted absences.""" construction, so they are the only permitted absences."""
# REAL table names, as _BACKED_UP holds them — not the shorter keys the
# payload uses for the same sections. Getting this wrong is what the guard
# caught on its own first run.
join_tables = { join_tables = {
"rulebook_subscriptions", "rule_suppressions", "project_rulebook_subscriptions", "project_rule_suppressions",
"topic_suppressions", "rulebook_exclusions", "rule_systems", "project_topic_suppressions", "project_rulebook_exclusions",
"rule_systems",
} }
covered = set(_column_guard_targets()) | join_tables covered = set(_column_guard_targets()) | join_tables
assert set(backup._BACKED_UP) - covered == set() assert set(backup._BACKED_UP) - covered == set()