fix(guard): parse gateway bypass query booleans#4926
fix(guard): parse gateway bypass query booleans#4926NathanFlurry wants to merge 1 commit intosqlite-soak/vfs-staging-cache-ttlfrom
Conversation
Code Review: fix(guard): parse gateway bypass query booleansOverviewThis PR fixes a bug where the The fix adds special-case parsing for What's Good
Concerns1. Silent fallback on invalid values produces a confusing error When A better path is to return an explicit error instead of falling back: "bypass_connectable" => match parse_query_bool(value) {
Some(b) => serde_json::Value::Bool(b),
None => return Err(/* descriptive error about invalid boolean value */),
},2. Maintenance risk: typed field list is split from the struct
A more robust long-term approach would be to use 3. No tests There are no new tests covering:
Given this is a targeted bug fix for a specific parsing path, at minimum a unit test on Minor
SummaryThe fix is correct and minimal. Two actionable items before merge: (1) handle invalid boolean values explicitly with a descriptive error instead of silently falling back to a string that produces an opaque serde error, and (2) add at least a unit test for the happy path and the invalid-value path. |
f7d89ed to
6b85d8c
Compare
48cc3bb to
17e8f52
Compare
f8acbf0 to
0db4613
Compare
|
Landed in main via stack-merge fast-forward push. Commits are in main; closing to match. |

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist: