Use new ember-resolver instead of ember/resolver #31
Conversation
|
Just updating my Ember app to 1.13.8 and getting rid of all the deprecation warnings and came across this one. When will ember/resolver be replaced to ember-resolver? I really didn't want to fork the repo or use someone else's fork just for this change. Do you know when this will be updated? |
|
I really don't know. It should be fine to merge this, the build is failing for other reasons though. I had not yet time to test this for older ember releases and I haven't researched how to make both variants work yet. |
|
Failures are unrelated to this so going to merge, I'm seeing similar failures in other addons where the container/owner is not found in tests but works fine in development. Our flat has just been flooded, so my time to investigate tonight is limited, but will take a look more hopefully over the weekend. |
Use new ember-resolver instead of ember/resolver
|
Sorry to hear that Richard. Thanks a lot for the merge. Hope everything turns out OK with the flat. |
|
Regarding test failures, haven't looked into it thoroughly yet, but there has been a change on how to do lookups that may be related: emberjs/guides#982 |
This should remove the deprecation warning in the latest Ember release v2.2.0.
I only tested against 2.2.0, I will test against the older version later today, I just wanted to file the pull request to make sure I don't forget it later on.