Skip to content

Conversation

@untitaker
Copy link
Member

@untitaker untitaker commented Jan 25, 2019

Fix ISSUE-296

@untitaker untitaker requested review from billyvg and jan-auer January 25, 2019 09:20
Copy link
Member

@billyvg billyvg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Does this address a sentry issue? A PR description would be nice to have.

result += '"';
return result;
let queryObj = {};
for (let [k, v] of query) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we not stringify query directly?

@untitaker
Copy link
Member Author

Sorry, I forgot to link the JIRA issue. I'll try to make a brief summary here because the JIRA ticket contains too much PII

The gist is that we fixed #11606, but a similar bug happened somewhere else: A querystring like foo=bar&baz=bam would previously be sent as string through the API. We changed this to send a list of lists, but didnt consider testing the UI.

Right now the clickable URL is broken in all events that have a querystring. It serializes out the above querystring as foo,bar,baz,bam, which is nonsense.

@untitaker untitaker merged commit 44797b1 into master Jan 28, 2019
@untitaker untitaker deleted the fix/more-query-string-stuff branch January 28, 2019 12:56
@github-actions github-actions bot locked and limited conversation to collaborators Dec 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants