Repository navigation
v2.2.1
Bug fixes
- The Explorer client percent-encodes caller-supplied path ids and custom data-filter keys, across the twelve path-building methods and the query-string builder. A sale id, marketplace or collection name, or
DataOptionskey carrying/,?,#,&, or=used to escape its own segment and reshape the request path or query. Hostile input now stays a value. (#17)
Other changes
- Typed data filters travel as
data%3Anumber.fieldrather thandata:number.field. Standards query parsers percent-decode keys before matching, so servers see the same key. This is confirmed against the live API, where the encoded and raw forms return identical filtered rows. The plaindata.fieldform is unchanged. (#17)
Commits
- ccc9217 fix: percent-encode caller-supplied path ids and data-filter keys in the Explorer client (#17)
- e2e96c5 chore(release): 2.2.1
Full changelog: v2.2.0...v2.2.1