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

updates & cleanup #19

Closed
wants to merge 2 commits into from

Conversation

stefanpenner
Copy link
Contributor

  • upgrade to latest ember-cli
  • remove unused files
  • upgrade to some fancy ES2015 syntax
  • enable ember-try
  • still some test failures, i'll revisit later today.
  • fix deprecations
    • remove ObjectController usage.

* upgrade to latest ember-cli
* remove unused files
* upgrade to some fancy ES2015 syntax
* enable ember-try
@Robdel12
Copy link
Collaborator

Looks good! The fail is related to: emberjs/ember.js#11221 (just incase anyone stumbles upon this.)

@stefanpenner
Copy link
Contributor Author

@Robdel12 ah ok. Is that the source of all the failures or just this one?

@Robdel12
Copy link
Collaborator

Yeah that's what it looks like. I'm on mobile and the Travis output is hard to read so I might have missed something :p

@stefanpenner
Copy link
Contributor Author

Yeah that's what it looks like. I'm on mobile and the Travis output is hard to read so I might have missed something :p

Ya I can confirm (well for stable releases, canary is another story...)

@stefanpenner
Copy link
Contributor Author

@Robdel12 as stable failure is expected, what would you suggest the next steps should be?

I'll work on the other failures, and report accordingly. The reality is, this isn't much different then the state on master currently..

@Robdel12
Copy link
Collaborator

@stefanpenner Man I didn't even look at canary's test fails. Glimmer did a number on it :P

I'm not sure how to go about fixing the fails on the other versions (1.11, 1.12). Since it seems to be an ember bug It'd be nice to see that fixed so we can get this merged in and work on canary related fails.

I'd love to help with the ember bug but I'm not sure where it's busted. I dug around in the source for an hour and didn't come out with anything.

'ember': 'canary'
}
}
]
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we add Ember 1.10 to this?

@stefanpenner
Copy link
Contributor Author

@Robdel12 added, it is also the only one to pass.

@Robdel12
Copy link
Collaborator

@stefanpenner I expected that. Really interested what changed between 1.10 vs 1.11 with binding attrs.

@nikz
Copy link

nikz commented May 29, 2015

@Robdel12 @stefanpenner is there anything I can help out with to get this PR merged? Keen to upgrade to ember-cli 0.2.4.

@Robdel12
Copy link
Collaborator

@nikz you can update to ember cli 0.2.4 but you can't update to Ember 1.11+ yet if you are binding the form attribute to your select.

There is a running bug ticket on ember that @stefanpenner and friends have been doing some great work on :) emberjs/ember.js#11221 (comment)

@stefanpenner
Copy link
Contributor Author

@Robdel12 my suggestion would be to merge this. As it only accurately represents the current state. We can likely get the form fix in shortly to ember, we just have to settle on which way to solve it

Is there anything with this pr I can improve?

@cowboyd
Copy link
Collaborator

cowboyd commented May 29, 2015

How about we just conditionally skip the test on the versions that are failing.

@stefanpenner
Copy link
Contributor Author

How about we just conditionally skip the test on the versions that are failing.

but they are actually legitimately failing. Should we maybe move them to allowed failures?

@Robdel12
Copy link
Collaborator

Robdel12 commented Jul 3, 2015

Closing this since we've had a couple PRs that do this.

@Robdel12 Robdel12 closed this Jul 3, 2015
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.

4 participants