Skip to content

routes/github-authorize: Fix queryParams code #2029

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

Merged
merged 1 commit into from
Dec 20, 2019
Merged

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Dec 20, 2019

Accessing queryParams on the transition object was never officially public API in Ember.js, and has been deprecated in Ember.js v3.6 (see https://deprecations.emberjs.com/v3.x#toc_transition-state). Since it was only considered "intimate" API its removal was done in v3.9 instead of v4.0. Since we skipped both of these versions we unfortunately never saw the corresponding deprecation warning... 😞

But even if we did upgrade to v3.8 LTS in between, we probably still would have missed it, because the github-authorize route is only called in a popup window where the usual DevTools console is not attached, and we unfortunately don't have any test for the login flow (yet!).

Closes #2027, Resolves #2028

@carols10cents r?

@Turbo87 Turbo87 added C-bug 🐞 Category: unintended, undesired behavior A-frontend 🐹 labels Dec 20, 2019
@rust-highfive
Copy link

r? @carols10cents

(rust_highfive has picked a reviewer for you, use r? to override)

@carols10cents
Copy link
Member

Works for me locally!!! Thank you thank you thank you!!

@bors r+

@bors
Copy link
Contributor

bors commented Dec 20, 2019

📌 Commit 1989917 has been approved by carols10cents

bors added a commit that referenced this pull request Dec 20, 2019
routes/github-authorize: Fix `queryParams` code

Accessing `queryParams` on the `transition` object was never officially public API in Ember.js, and has been deprecated in Ember.js v3.6 (see https://deprecations.emberjs.com/v3.x#toc_transition-state). Since it was only considered "intimate" API its removal was done in v3.9 instead of v4.0. Since we skipped both of these versions we unfortunately never saw the corresponding deprecation warning... 😞

But even if we did upgrade to v3.8 LTS in between, we probably still would have missed it, because the `github-authorize` route is only called in a popup window where the usual DevTools console is not attached, and we unfortunately don't have any test for the login flow (yet!).

Closes #2027, Resolves #2028

@carols10cents r?
@bors
Copy link
Contributor

bors commented Dec 20, 2019

⌛ Testing commit 1989917 with merge da4ede8...

@bors
Copy link
Contributor

bors commented Dec 20, 2019

☀️ Test successful - checks-travis
Approved by: carols10cents
Pushing da4ede8 to master...

@bors bors merged commit 1989917 into rust-lang:master Dec 20, 2019
@Turbo87 Turbo87 deleted the qp branch January 3, 2020 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend 🐹 C-bug 🐞 Category: unintended, undesired behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrading ember-source from 3.1.2 to 3.15.0 breaks logging in
4 participants