We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When passing a string variable to runPersistedQuery, variablesString should be formatted without underquoting it.
runPersistedQuery
variablesString
Example:
const variables = { slug: 'aaa' } await aemHeadlessClient.runPersistedQuery(path, variables)
variablesString should finally be assigned:
';slug=aaa'
as it is under @adobe/[email protected].
@adobe/[email protected]
variablesString is assigned:
';slug="aaa"'
...with the extra double quotes. Apparently, a bug introduced in #41.
@adobe/[email protected] and 3.3.1
3.3.1
The text was updated successfully, but these errors were encountered:
I think this problem was introduced in #50 here Its correct for an object
JSON.stringify({hello: "world"}) == '{"hello":"world"}'
but not for a simple string value
JSON.stringify("hello") == '"hello"'
Sorry, something went wrong.
fix: adobe#51 persisted query string parameter encoding
db0d59c
This is also affecting my project, it looks like the PR #53 is all good to be merged? Can it please be applied ?
Cheers
8b5aeeb
No branches or pull requests
Expected Behaviour
When passing a string variable to
runPersistedQuery
,variablesString
should be formatted without underquoting it.Example:
variablesString
should finally be assigned:';slug=aaa'
as it is under
@adobe/[email protected]
.Actual Behaviour
variablesString
is assigned:';slug="aaa"'
...with the extra double quotes. Apparently, a bug introduced in #41.
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
@adobe/[email protected]
and3.3.1
Sample Code that illustrates the problem
Logs taken while reproducing problem
The text was updated successfully, but these errors were encountered: