Skip to content

fix: preserve special characters in title query filters - #153

Open
Shubham-Padkonde wants to merge 1 commit into
1Password:mainfrom
Shubham-Padkonde:fix/encode-title-query-filters
Open

Shubham-Padkonde wants to merge 1 commit into
1Password:mainfrom
Shubham-Padkonde:fix/encode-title-query-filters

Conversation

@Shubham-Padkonde

Copy link
Copy Markdown

Title filters are concatenated directly into the URL, so an item named with a + is queried as though it contained a space. Ampersands split the query, fragments truncate it, and existing percent sequences are decoded prematurely.

Encode the query key/value in the shared PathBuilder. Both sync and async item/vault lookups now preserve the original filter value. Extend their existing tests with reserved characters and Unicode titles, matching the decoded HTTP query rather than an unescaped URL string.

Fixes #123.

Validation: all 60 tests pass. Four sync/async item/vault regression cases fail before the fix. git diff --check passes. The suite reports one pre-existing asyncio-marker warning on a synchronous timeout test. Tests use mocked Connect responses; no live Connect server was used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

get_item_by_title() will not find the item with title containing +

1 participant