audit the whole app for stupid cases of missing functionality or basic things like this (like the stats panel at the top that i requested).
What is wrong: the UI gives one thing several names, or a name that says something other than what it means.
The resubmit message says "this source has no active targets" (resubmitOutcome in internal/handlers/event_resubmit.go). Everywhere else in the UI the thing is a webhook.
The database target type is "Database" in the type list and on its badge, but its setting is "Archive expiry" on the add form and "Archive Expiry" on the edit page and in the target list. The README calls it an archive too.
"Max retries" holds the total number of attempts, not retries, so its own help text has to explain that "a value of 3 makes three attempts in all".
The navigation bar says "Login" and "Logout", while the sign-in page says "Sign in to your account" and "Sign In".
("Event Log" and "View All" for the same page are already handled by #367.)
Definition of done:
The resubmit message says "webhook".
The database type has one display name, used on its badge, in the type list and in its setting labels. The manager picks it on this issue before work starts.
The retry field is labelled for what it holds, for example "Delivery attempts", with its help text rewritten to match, on the add form, the edit page and in the target list. The stored value and its meaning do not change.
Sign-in and sign-out use one wording everywhere.
The PR lists every string it changed. Tests are updated to match.
PRIORITY: from the owner's audit request of 1 October (#377), in the tier of #367 to #376.
Model: opus-5-5
Owner's request, https://git.eeqj.de/sneak/webhooker/issues/377 (chat, 2026-10-01):
> audit the whole app for stupid cases of missing functionality or basic things like this (like the stats panel at the top that i requested).
What is wrong: the UI gives one thing several names, or a name that says something other than what it means.
- The resubmit message says "this source has no active targets" (`resubmitOutcome` in `internal/handlers/event_resubmit.go`). Everywhere else in the UI the thing is a webhook.
- The `database` target type is "Database" in the type list and on its badge, but its setting is "Archive expiry" on the add form and "Archive Expiry" on the edit page and in the target list. The README calls it an archive too.
- "Max retries" holds the total number of attempts, not retries, so its own help text has to explain that "a value of 3 makes three attempts in all".
- The navigation bar says "Login" and "Logout", while the sign-in page says "Sign in to your account" and "Sign In".
("Event Log" and "View All" for the same page are already handled by https://git.eeqj.de/sneak/webhooker/issues/367.)
Definition of done:
- The resubmit message says "webhook".
- The `database` type has one display name, used on its badge, in the type list and in its setting labels. The manager picks it on this issue before work starts.
- The retry field is labelled for what it holds, for example "Delivery attempts", with its help text rewritten to match, on the add form, the edit page and in the target list. The stored value and its meaning do not change.
- Sign-in and sign-out use one wording everywhere.
- The PR lists every string it changed. Tests are updated to match.
PRIORITY: from the owner's audit request of 1 October (https://git.eeqj.de/sneak/webhooker/issues/377), in the tier of https://git.eeqj.de/sneak/webhooker/issues/367 to https://git.eeqj.de/sneak/webhooker/issues/376.
Model: opus-5-5
clawbot
self-assigned this 2026-10-01 22:06:26 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Owner's request, #377 (chat, 2026-10-01):
What is wrong: the UI gives one thing several names, or a name that says something other than what it means.
resubmitOutcomeininternal/handlers/event_resubmit.go). Everywhere else in the UI the thing is a webhook.databasetarget type is "Database" in the type list and on its badge, but its setting is "Archive expiry" on the add form and "Archive Expiry" on the edit page and in the target list. The README calls it an archive too.("Event Log" and "View All" for the same page are already handled by #367.)
Definition of done:
databasetype has one display name, used on its badge, in the type list and in its setting labels. The manager picks it on this issue before work starts.PRIORITY: from the owner's audit request of 1 October (#377), in the tier of #367 to #376.
Model: opus-5-5