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

Updated to ember-2.4 and beyond #23

Merged
merged 1 commit into from
Jun 7, 2016

Conversation

kiwiupover
Copy link
Collaborator

@kiwiupover kiwiupover commented Jun 2, 2016

Happy JSCS
Upgraded ember-cli
Updated tests to use components
Added ember try for 1.11 -> 1.13 and 2.0, 2.1, 2.2, 2.3, 2.4 -> Canary

This PR DROPS support for Ember 1.10 and below. Ember 2.3 has a bug in the router so this PR supports 2.4 through Canary interestingly Ember 2.0, 2.1 and 2.2 pass the tests so I could look into what the actual issues are in 2.3.

@mike-north I understand this is a big PR let me know if you want anything explained.

I will follow with a README update too.

Closes #19 #18

@@ -37,7 +37,7 @@ prototype.activateRoute = function activateRoute(route) {

prototype.routeFinishedSetup = function routeFinishedSetup(route) {
const endTime = t();
const [r] = this.routes.filter(r => r.name === route.routeName);
const [r] = this.routes.filter((r) => r.name === route.routeName);
Copy link
Owner

Choose a reason for hiding this comment

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

const shouldn't be used except in the module closure

@mike-north
Copy link
Owner

This PR DROPS support for Ember 1.10 and below. Ember 2.3 has a bug in the router so this PR supports 2.4 through Canary interestingly Ember 2.0, 2.1 and 2.2 pass the tests so I could look into what the actual issues are in 2.3.

I'm ok with this, but for compatibility reasons (maybe there's someone out there w/ a patched router, or an app that doesn't hit the bug), let's aim for generalized > 1.10 compatibility. Don't worry about addressing the 2.3 bug, except to:

  • Add something in the readme making developers aware of this limitation

@mike-north
Copy link
Owner

Also thanks for all this work! Great to resurrect this addon from the ashes

@kiwiupover kiwiupover force-pushed the updated-to-ember2.4 branch 4 times, most recently from 080aa29 to 3caaf12 Compare June 2, 2016 15:21
updated ember-try
upgraded ember-cli
updated tests to use components
fixed test across 1.13 > 2.5
added ember try for 2.4 and 2.5
@kiwiupover kiwiupover force-pushed the updated-to-ember2.4 branch from 3caaf12 to b82ac3b Compare June 2, 2016 16:22
@kiwiupover
Copy link
Collaborator Author

kiwiupover commented Jun 2, 2016

@mike-north This is ready again.

I have updated the readme, found a typo in the components, pulled ember-perf-handlebars and made the CI much faster. Now I'm drinking coffee.

Last thing I bumped the version number too 0.1.0

@kiwiupover
Copy link
Collaborator Author

@mike-north is there something else todo with this PR?

@mike-north mike-north merged commit 5d5bb47 into mike-north:master Jun 7, 2016
@mike-north mike-north mentioned this pull request Jun 7, 2016
@mike-north
Copy link
Owner

Released as 0.1.0. Thanks @kiwiupover!

@mike-north mike-north mentioned this pull request Jun 7, 2016
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.

3 participants