Release v22.28.1

Changed

• Query argument parsing is stricter: values that previously fell back silently now return HTTP 400, including ?flag=1 or ?flag=yes for a boolean, overflowing integers, whitespace-only values, invalid nullable value types that used to become null, and invalid concept values (including nullable or defaulted concepts). Clients must send valid values or omit optional arguments.
• The new public InvalidQueryArgument exception represents an invalid supplied query argument; QueryHttpExtensions.GetQueryArguments can now throw it. Invalid collection elements use the same named malformed-request validation shape.

Fixed

• Invalid scalar, concept, and collection arguments on GET and QUERY endpoints now return HTTP 400 with a named malformed-request validation error instead of invoking model-bound or controller queries with default values or reporting invalid values as missing. (#2794)