Fix: Handle "/" character in query names to prevent NotFoundError #116
+6
−2
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.
Summary
This pull request fixes the NotFoundError that occurs when query names contain the "/" character.
Details
As reported in the issue #106, query names with the "/" character were not being properly encoded, leading to an API endpoint not found error. The issue was due to the default behavior of the
urllib.parse.quote
function, which does not encode the "/" character.Fix
Updated the
create_url
function intdclient/util.py
as follows:This change ensures that all characters, including "/", are correctly encoded.