Debian Patches
Status for golang-github-pb33f-jsonpath/0.8.2-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Accept-true-false-null-as-dot-notation-member-names.patch | Accept true/false/null as dot-notation member names The RFC 9535 JSONPath compliance test suite expects $.true, $.false, and $.null to be valid shorthand property name selectors. However, the tokenizer emits TRUE, FALSE, and NULL tokens for these keywords, which were only handled in filter-expression contexts (parseLiteral) but not in dot-notation inner segments (parseInnerSegment). Fix by accepting TRUE, FALSE, and NULL tokens in parseInnerSegment, reading the Literal field which already contains the correct string ("true", "false", "null"). |
Reinhard Tartler <siretart@tauware.de> | no | 2026-06-13 | ||
| 0002-fix-update-test-snapshots-for-yaml.v4-word-wrapping-.patch | fix: update test snapshots for yaml.v4 word-wrapping behavior Newer versions of go.yaml.in/yaml/v4 introduce changes to how yaml.Node structures are serialized to text. Specifically, long string fields (like description fields in OpenAPI specs) are now automatically word-wrapped at 80 columns. The tests in pkg/overlay assert equality by comparing serialized YAML nodes against hardcoded snapshot files (openapi-overlayed.yaml and overlay-generated.yaml). Because the previous snapshots contained unwrapped long lines, these tests failed when building with the upgraded YAML parser. This commit updates the yaml.v4 dependency to v4.0.0-rc.5 and regenerates the test snapshots so they match the newly expected word-wrapped format, preventing CI failures in environments using newer dependencies. |
Reinhard Tartler <siretart@tauware.de> | yes | 2026-06-15 |
All known versions for source package 'golang-github-pb33f-jsonpath'
- 0.8.2-2 (sid)
