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

Upgrade to latest ember versions & fix all warnings/errors #157

Merged
merged 3 commits into from
Feb 20, 2018
Merged

Upgrade to latest ember versions & fix all warnings/errors #157

merged 3 commits into from
Feb 20, 2018

Conversation

sivakumar-kailasam
Copy link
Contributor

@sivakumar-kailasam sivakumar-kailasam commented Feb 12, 2018

Used the codemod to migrate to latest version. Then fixed eslint errors & ember-cli-page-object warnings.

@sivakumar-kailasam
Copy link
Contributor Author

@chrislopresto Please let me know if this PR needs improvement.

@chrislopresto
Copy link
Owner

@sivakumar-kailasam This PR looks great, thanks! What codemod did you use?

We just finally merged #100 which was pretty big, so this is going to need a rebase. If you have some time over the next few days, great. If not, no worries... I could hop in to resolve the merge conflicts.

Thoughts?

@sivakumar-kailasam
Copy link
Contributor Author

@chrislopresto I used ember-cli-update for the upgrade. I also used ember-modules-codemod for import rewrites on rebase conflicts.

Rebased against latest changes in master. Hope this helps

Copy link
Owner

@chrislopresto chrislopresto left a comment

Choose a reason for hiding this comment

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

Thanks so much for doing this! I hadn't fully wrapped my head around some of resolutions to the ember linter errors... thanks for demonstrating the way.

I left some comments, mainly centering around the ember-try config. Let me know if you don't have time to tweak and I can pick up when I'm working on things this week.

Cheers!

.travis.yml Outdated
@@ -25,11 +25,8 @@ env:
matrix:
# we recommend new addons test the current and previous LTS
# as well as latest stable release (bonus points to beta/canary)
- EMBER_TRY_SCENARIO=ember-lts-2.4
- EMBER_TRY_SCENARIO=ember-lts-2.8
Copy link
Owner

Choose a reason for hiding this comment

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

For the time being, I'd like to leave 2.4 and 2.8 in the ember-try config so we remain aware of freestyle's compatibility in CI. We're only officially supporting the trailing 2 LTS releases (2.16 and 2.18 technically), so we'll include 2.4 and 2.8 in the allow_failures section below. Perhaps we should also add 2.12 as an allowed failure while we're at it.

.travis.yml Outdated
- EMBER_TRY_SCENARIO=ember-lts-2.12
- EMBER_TRY_SCENARIO=ember-lts-2.16
- EMBER_TRY_SCENARIO=ember-lts-2.18
Copy link
Owner

Choose a reason for hiding this comment

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

Since 2.18 is an LTS release, let's leave this in.

.travis.yml Outdated
@@ -38,8 +35,6 @@ env:
matrix:
fast_finish: true
allow_failures:
- env: EMBER_TRY_SCENARIO=ember-lts-2.4
- env: EMBER_TRY_SCENARIO=ember-lts-2.8
Copy link
Owner

Choose a reason for hiding this comment

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

These would come back in, too.

@@ -19,15 +19,15 @@ export default Ember.Component.extend({
actions: {
toggleCheckbox() {
let newValue = !this.get('value');
this.attrs.changeValueTo(newValue);
Copy link
Owner

Choose a reason for hiding this comment

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

Nice... thanks!

module.exports = {
useYarn: true,
Copy link
Owner

Choose a reason for hiding this comment

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

I think we should keep this useYarn flag, if only for speed. 🙂

'ember-source': null
}
}
},
Copy link
Owner

Choose a reason for hiding this comment

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

These 2.4, 2.8, and 2.18 entries would come back as well.

jsconfig.json Outdated
@@ -0,0 +1 @@
{"compilerOptions":{"target":"es6","experimentalDecorators":true},"exclude":["node_modules","bower_components","tmp","vendor",".git","dist"]}
Copy link
Owner

Choose a reason for hiding this comment

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

This file comes from VS Code, right? Should we gitignore it?

package.json Outdated
"broccoli-merge-trees": "^2.0.0",
"broccoli-writer": "^0.1.1",
"ember-cli-babel": "^6.6.0",
"ember-cli-htmlbars": "^2.0.3",
"ember-cli-sass": "^6.1.3",
"ember-cli-sass": "^7.1.4",
Copy link
Owner

Choose a reason for hiding this comment

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

No need for any change in this PR... just calling this out for posterity:

Some folks have been having problems with ember-cli-sass dependency resolution based on their local app's setup. I believe ember-cli-sass 7 (released in July) has some breaking changes from ember-cli-sass 6, so I don't know if this upgrade will help or hurt. Regardless, I'm going to change ember-freestyle's scss to vanilla CSS soon, so I say we roll with this as is for the time being.

@@ -1,52 +0,0 @@
{
Copy link
Owner

Choose a reason for hiding this comment

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

👍

@sivakumar-kailasam
Copy link
Contributor Author

@chrislopresto addressed all the review comments with the latest commit. Should be gtg :)

@sivakumar-kailasam
Copy link
Contributor Author

https://github.com/ember-cli/eslint-plugin-ember/tree/master/docs/rules is a good place to learn the reasoning behind each of the rules brought in by that plugin. Its well documented.

@chrislopresto chrislopresto merged commit 29f5717 into chrislopresto:master Feb 20, 2018
@chrislopresto
Copy link
Owner

Thanks!

@sivakumar-kailasam
Copy link
Contributor Author

@chrislopresto can you please publish a new version? I have a PR on another repo that was waiting on this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants