-
Notifications
You must be signed in to change notification settings - Fork 473
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
Differentiate between compatibility patches and pure warnings #472
Comments
I agree we're doing two different things here, but wonder what the solution is for this. Would we create another flag like |
Yeah, naming is hard. ;) Would a single API be enough, considering there are use cases both to only enable patches required to make the current major version of jQuery work post-upgrade and to only enable deprecation warnings for a future major? We could also bake it into Then we'd just need to keep a list of compat patches and compare those special keys against that. Thoughts? |
jQuery Migrate does two things:
It makes sense to differentiate these two for a few reasons:
We should have an easier way to only enable patches required to address before removing Migrate or to only enable the ones preparing for the next major version.
Thoughts, @dmethvin @timmywil @gibson042?
The text was updated successfully, but these errors were encountered: