-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Project Svelte] Deprecation Introduction Hitlist #15062
Comments
Is the property still |
I'm working on this, I've gone through most of the changelog and still I have a few to solve. I'll be uploading a PR soon with the part I get done by then. |
@Serabe We basically just need the mapping from deprecation ID to version. We are going to have deprecation flags that take a semver version. This semver version will get turned into a bool based on what the consuming app says it supports. |
If you just need the mapping, this is the list:
If you don't need the actual |
From the work (https://gist.github.com/andyhot/0c574101afc3ff25f95469453447930f) i had done for #14811, here's my (partial) findings:
The differences I see with @Serabe 's findings:
fyi, all of the versions i had found were from tracking down the tagged commits hence the more detail (though i can just be plain wrong in same cases where code was moved to different files) |
So I think I need verification on these @rwjblue and if we should just go cleanup all the 1.13.0 flags. There is also some
|
yep, all of those can can be cleaned up |
Can this be closed? |
@andyhot @chadhietala @locks @rwjblue closing for now, perhaps reopen or create a new issue to continue this effort if there is anything remaining. |
Wanted
We need to know in which versions of Ember these deprecations were introduced. Please simply report the version a specific id was introduced. To ensure that we don't have overlapping efforts, please state what deprecation you are investigating before you do the work.
Why
With the eventual introduction of Svelte builds, there will be a mechanism to say "strip out any code for deprecated features from 2.0 to 2.8". However, to enable this range-based decision, we need both the start of the range.
How
Ways to find deprecations:
deprecate()
method in the codebase[DEPRECATE]
and[DEPRECATION]
tags in the CHANGELOG.Deprecation IDs
The text was updated successfully, but these errors were encountered: