-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
Port code to ember-rfc176-data new format #142
Conversation
7b2e462
to
3153224
Compare
this is a problem, since we should still warn about this even if there is no equivalent in the new mappings... 🤔 |
Ya, we should explicitly support having |
Then either the old-shims file should not be removed or the data that was lost in translation brought back. |
Hmm, not sure I'm following. All of the old shims data is included in the new |
Chatted with @Serabe in slack about this, and summarized in ember-cli/ember-rfc176-data#37 (comment). |
we might also want to think about adding an |
Right. |
Ya, but I actually think a general rule for |
I tend to disagree. The |
Yep, totally agreed. At the moment we only have things that should have always worked, but I totally agree that at some future time we could deprecate a module in favor of some replacement that doesn't exist for certain Ember versions. This doesn't mean my suggested path forward is wrong 😉, it just means we need more data than For deprecations as of a specific Ember version, we should encode that into the updated |
what we could do is have a static list of module paths in this plugin that were part of |
I agree with @Turbo87, but having a static list of modules used in |
I don't understand why that would be a problem? 🤔 |
c3143e3
to
fa1bc9f
Compare
I need to keep the force upgrade of |
Ready to update to point at [email protected] now that it is published. |
@rwjblue done! |
.travis.yml
Outdated
@@ -8,6 +8,7 @@ node_js: | |||
cache: yarn | |||
|
|||
script: | |||
- yarn upgrade ember-rfc176-data |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be needed any more...
package.json
Outdated
@@ -53,7 +53,7 @@ | |||
"jest": "^20.0.4" | |||
}, | |||
"dependencies": { | |||
"ember-rfc176-data": "^0.2.7", | |||
"ember-rfc176-data": "~0.3.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably still be ^0.3.0
(it just has the same effect as ~0.3.0
in this case)
This PR adapts the code to the new format in ember-cli/ember-rfc176-data#37 This also removes a line testing an old shims not ported to new format.
8a12d8b
to
5468e62
Compare
I just updated with:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you add a test for Ember.String.htmlSafe
to check that we're handling the deprecated
flag correctly?
sure, also still working on a few of the remaining failures (seem related to destructuring) |
We already had a test for |
hmm, about the |
yes, but not now 😄, both |
This PR adapts the code to the new format in
ember-cli/ember-rfc176-data#37
This also removes a line testing an old shims not ported to new format.