Feature Updation
This commit is contained in:
@@ -11,11 +11,14 @@ says so, and every assertion below is ultimately about one of two failures -
|
||||
* something running that nobody approved, and
|
||||
* a file being lost, or run twice, on its way out of the inbox.
|
||||
|
||||
The response SHAPES are asserted literally rather than loosely, because
|
||||
frontend/src/pages/InboxPanel.jsx was written against this contract before the
|
||||
backend existed. `submission_id`, `file_id`, `pending_count` and the `dismissed`
|
||||
count are read by name there; a rename that only this file catches is cheap, and
|
||||
one that nothing catches is a blank admin tab with no error.
|
||||
The response SHAPES are asserted literally rather than loosely, because the
|
||||
frontend was written against this contract before the backend existed.
|
||||
`submission_id`, `file_id`, `pending_count` and the `dismissed` count are read
|
||||
by name in frontend/src/pages/UploadResultsPanel.jsx - the approval gate lives
|
||||
inside that panel now, revealed only when `pending_count` is above zero, since
|
||||
UPLOAD_AUTORUN=true leaves the inbox permanently empty. A rename that only this
|
||||
file catches is cheap, and one that nothing catches is a blank admin tab with no
|
||||
error.
|
||||
"""
|
||||
from __future__ import annotations
|
||||
|
||||
|
||||
Reference in New Issue
Block a user