ge-aerospace/shopdb-flask
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Let a site choose the order its board rows run in

Browse Source 
Rows ran in display-style order and then alphabetically, so what led the screen
was an accident of styling and the alphabet - a new type called Awareness
landed above Recertification for no better reason than the letter A.

Each type now carries a board position, lowest first, set on the Notification
Types page. The migration seeds Recognition at 10 and Recertification at 20 and
leaves everything else at 100, so an existing board keeps the order sites
already expect. Steps of ten leave room to slot a row in without renumbering
the rest.

A row shared by several types sits wherever its earliest-ordered type puts it,
so a category moves as a unit.
This commit is contained in:
cproudlock
2026-08-08 14:20:35 -04:00
parent adb8542018
commit 442a631557
6 changed files with 208 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
tests/test_plugin_migrations.py
View File

@@ -68,7 +68,7 @@ EXPECTED_HEAD_REVISION['network'] = 'network0002model'
EXPECTED_HEAD_REVISION['printedparts'] = 'printedparts0004txnrev'
# notifications indexes businessunitid, then adds the per-type grace window and
# the shared board category.
EXPECTED_HEAD_REVISION['notifications'] = 'notifications0004category'
EXPECTED_HEAD_REVISION['notifications'] = 'notifications0005boardorder'
# Plugins built after the cutover: their 0001 baseline really creates tables the
# core chain never owned.