Minor settings problems now show only in /status instead of padding the invalid-settings list.
What's wrong with this entry?
Settings validation can now mark a problem as informational or as fatal at startup. Informational ones show up in /status but no longer pad out the "Invalid settings" list or the invalid-entries dialog; fatal ones are logged at error level.
- Validation callbacks flag an issue as status-only or startup-fatal; status-only issues are collected separately as status notices.
- The invalid-entries dialog and the "Invalid settings" list now contain only real validation failures.
statusNotices
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
/status shows a "Session kind" row
Both mention status
-
v2.1.229
Version bumped to 2.1.229
Both mention status
-
v2.1.238
Durable wake subscriptions now say why they failed
Both mention status