Skip to content
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

UI: Ember 2.18 -> Ember 3.0 #5422

Merged
merged 21 commits into from
Mar 15, 2019
Merged

UI: Ember 2.18 -> Ember 3.0 #5422

merged 21 commits into from
Mar 15, 2019

Conversation

DingoEatingFuzz
Copy link
Contributor

This is step one in a process to upgrade to the latest Ember.js LTS version (3.4).

Major ember upgrades aren't as scary as minor upgrades, so this is a relatively safe PR.

The bulk of these changes were done with codemods that rewrote tests to the new testing style. The codemods aren't perfect and couldn't know about some of the custom testing stuff in Nomad, so there is also ~1000 lines of changes made by hand.

@DingoEatingFuzz DingoEatingFuzz requested a review from a team March 14, 2019 18:41
Copy link

@alisdair alisdair left a comment

Choose a reason for hiding this comment

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

It's really awesome that no app code had to change for this PR! I skimmed quite a lot of the changes because they looked fairly mechanical, but everything I read seemed good. Useful context to have for our hopefully-imminent upgrade process.

@@ -21,7 +21,7 @@ module.exports = function(environment) {
},

APP: {
blockingQueries: true,
blockingQueries: false,

Choose a reason for hiding this comment

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

Is this change related to the upgrade?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nope! Good catch.


hooks.beforeEach(function() {
this.subject = function() {
return this.owner.factoryFor('service:breadcrumbs').create();

Choose a reason for hiding this comment

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

This boilerplate for unit testing a service is kind of a bummer, but understandable.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There may be a better way to do this, such as something like setupSerializerTest(hooks), but I don't want to explore that until I make it to v3.4.

this.getCodeMirrorInstance = getCodeMirrorInstance(this.owner);

// Expose to window for access from page objects
window.getCodeMirrorInstance = this.getCodeMirrorInstance;
Copy link
Contributor

Choose a reason for hiding this comment

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

👌 nice

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Lol, it's not my proudest code, but Mirage also does this in a less obvious place. That's all the excuse I needed 😄

@DingoEatingFuzz DingoEatingFuzz merged commit 2232c80 into f-ui-ember-v3 Mar 15, 2019
@DingoEatingFuzz DingoEatingFuzz deleted the f-ui-ember-v3-3.0 branch March 15, 2019 19:54
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants