Fix POST static map option parsing - #2361
Draft
miakh wants to merge 2 commits into
Draft
Conversation
miakh
marked this pull request as draft
September 9, 2026 14:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2201.
POST JSON bodies can contain null optional fields. The merge treated those as real duplicate values, turning a query value such as border=white into an array and producing the reported invalid color warning. This change ignores nulls and normalizes the usual camelCase spellings of multi-word JSON options before the existing allowlist and merge logic run.
The regression tests compare the rendered PNGs, covering both lineCap/lineJoin from the body and query options alongside null body fields. Existing repeated path and marker behavior remains unchanged.
Validation: