We only had to update docs because we are already use the suggested YAML notation for JSON objects in query params. Additional reasons to keep this behavior: less work in JS, and remains backward-compatible with wider array of generated clients (soft interop with OpenAPI 2.x).
This PR does not change the spec, only clarifies docs about meta encoding when used for filtering + cleans up some intro text.
The goal here is to specify how
metashould be encoded so we can unblock https://github.com/ipfs/boxo/issues/381We only had to update docs because we are already use the suggested YAML notation for JSON objects in query params. Additional reasons to keep this behavior: less work in JS, and remains backward-compatible with wider array of generated clients (soft interop with OpenAPI 2.x).
cc @sanderpick @ipfs/wg-pinning-services