Fix deprecations from deprecation-workflow (and probably remove it at all)
See original GitHub issueWe have a plugin ember-cli-deprecation-workflow
which allows us to hide some deprecation messages. However if we want to be able to update Ember to the v3 we’d better fix those deprecations.
Some of them are brought the project dependencies, so if there aren’t new version of those dependencies let’s at least identify them at list them down.
If all deprecations will be fixed I suggest removing the plugin at all.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Handling Deprecations - Configuration - Ember Guides
Before any functionality or API is removed it first goes through a deprecation period where the functionality is still supported, but usage of...
Read more >Deprecating packages on nuget.org | Microsoft Learn
Deprecation workflow · To deprecate a package, go to Manage packages and select Deprecation: Go to deprecate package option · Select the version ......
Read more >Mailman 3 [Twisted-Python] [RFC] Deprecation Policy - Twisted ...
Important factors to bear in mind: - Maintaining deprecated APIs brings a cost to developers when they maintain code. - Removing APIs brings...
Read more >How do I turn off deprecation warnings in ember.js 2.3?
The source of these deprecations are most likely the libraries I use (legacy-controller, legacy-view, auth0, etc.) but regardless, I need to ...
Read more >Test-Driving Ember.js CRUD Operations - Semaphore CI
There is a deprecation workflow that we can follow. ... There is a fix in place for these, but there hasn't been any...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@stukalin I’ve been doing a lot of 2.18 updates for 2.x ember apps lately, I’d like to take this on. Ultimately I’d like to take on #1365 as well, but doing this first should make the PRs more manageable. Would you be open to marking #1365 as in progress as well to prevent some potentially ugly merge scenarios?
It looks like #1369 and #1366 are in progress and will be addressing some aspects of this PR. If those turn out to be non-trivial, I can wait for them to land on master and rebase.
This issue will be resolved once #1382 and #1369 are fixed. Hence, I’ll take away the
in progress
label for the time being.