-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
chore: Replace urlEncode with qs.stringify #84134
New issue
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
Conversation
❌ 10 Tests Failed:
View the top 3 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
This is the riskiest PR of the bunch -- I don't really trust our test coverage around it either. It might be better to go back to the other solution we proposed re: copying over the SDK function into sentry. Let's leave a comment in the function docs about what we're doing too |
return urlEncode({ | ||
...query, | ||
aggregates: query.aggregates.join(','), | ||
fields: query.fields?.join(','), | ||
columns: query.columns.join(','), | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be changed?
In preparation for upgrading to Sentry SDK v9, we need to replace
urlEncode
as it's deprecated. We are replacing it withstringify
fromquery-string
, which stringifies an object into a query string and sorts the keys, as well as URL encodes the keys and values.Merge after #84196