Skip to content
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

Deprecation Cleanup for 4.0 #19617

Closed
58 tasks done
kategengler opened this issue Jul 2, 2021 · 9 comments
Closed
58 tasks done

Deprecation Cleanup for 4.0 #19617

kategengler opened this issue Jul 2, 2021 · 9 comments
Milestone

Comments

@kategengler
Copy link
Member

kategengler commented Jul 2, 2021

PLEASE FLAG REMOVAL/CLEANUP PRs WITH [CLEANUP beta] IN THE PR TITLE.

The following are the deprecations in ember.js that are until 4.0 or earlier. Each item includes the id of the deprecation in backticks. Searching for this id in the source will find the invocations of that deprecation.

Remaining

VM Deprecations

🔒 Built-in Components

All should be 🔒 in #19806

Completed

@sandstrom
Copy link
Contributor

What do you think about deprecating Auto Location, is that something you'd like to get in before 4.0?

#19510

It's a fairly low-impact deprecation, in that the change required is a one-line change in the config. More details in that PR and the associated RFC.

But there is also no real rush, deprecating it doesn't "unlock" any new functionality, so could also wait until after 4.0 with merging it.

@kategengler
Copy link
Member Author

@sandstrom This is a list of already deprecated APIs that need to be removed for 4.0. At this point, the master branch is already 4.0, and so no newly added deprecations will make it into 3.x.

@nlfurniss
Copy link
Contributor

IE11 was removed in #19558

mixonic added a commit to mixonic/ember.js that referenced this issue Jul 18, 2021
mixonic added a commit to mixonic/ember.js that referenced this issue Jul 18, 2021
mixonic added a commit to mixonic/ember.js that referenced this issue Jul 18, 2021
mixonic added a commit to mixonic/ember.js that referenced this issue Jul 18, 2021
mixonic added a commit to mixonic/ember.js that referenced this issue Jul 18, 2021
@snewcomer
Copy link
Contributor

I can take this one since I did the original PR!

Implicit Injections implicit-injections

@snewcomer
Copy link
Contributor

I understand we are all busy. It is commendable even finding time to track issues, review and contribute code in our spare time. But is there any urgency to get this issue across the line in the coming weeks or is there an often talked about timeline not publicized? I have a few PRs open in glimmer that need review and would be happy to help with any remaining ones (once this tracking checkboxes are updated with where we are at).

@kategengler
Copy link
Member Author

There's definitely some urgency. 4.0 is the next release and ideally we would have gotten this all done before it even branched to beta.

Participation definitely drops over the summer and a few have commented that in the future we should avoid summer for major release pushes. We probably need to find a way to not have time-bound work for major releases.

@nlfurniss
Copy link
Contributor

Both Component manager capabilities prior to 3.13 and Modifier manager capabilities prior to 3.22 are covered by #19762

@xg-wang
Copy link
Contributor

xg-wang commented Oct 21, 2021

deprecate-router-events is covered by #19749 and ready for review

mixonic added a commit to kategengler/ember.js that referenced this issue Nov 12, 2021
Part of emberjs#19617

* Remove `someArray.addArrayObserver`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L532
* Remove `someArray.removeArrayObserver`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L548
* Remove `someArray.hasArrayObservers`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L571
* Remove `someArray.arrayContentWillChange`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L642
* Remove `someArray.arrayContentDidChange`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L670
  (also at
  https://github.com/emberjs/ember.js/pull/19833/files#diff-79a0015ca0e6a6c3661d9119f4caf6b26b111af6bb0e5bb784558631c599a81cL357)
* On the internal version of `addArrayObserver`, remove the optionality
  of `willChange` and `didChange` arguments to name the hooks. In
  framework code (and now in test) these are always provided.
* Retain basically all the test coverage of array observers since they
  remain used by `ArrayProxy` internally (and through that interface, in
  Ember Data).

Co-authored-by: Matthew Beale <[email protected]>
kategengler added a commit that referenced this issue Nov 15, 2021
Part of #19617

* Remove `someArray.addArrayObserver`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L532
* Remove `someArray.removeArrayObserver`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L548
* Remove `someArray.hasArrayObservers`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L571
* Remove `someArray.arrayContentWillChange`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L642
* Remove `someArray.arrayContentDidChange`
  https://github.com/emberjs/ember.js/pull/19833/files#diff-8116921433c6e1664250d5735e4f9daeb6ea9e00940783e0c4db7adf88aa8772L670
  (also at
  https://github.com/emberjs/ember.js/pull/19833/files#diff-79a0015ca0e6a6c3661d9119f4caf6b26b111af6bb0e5bb784558631c599a81cL357)
* On the internal version of `addArrayObserver`, remove the optionality
  of `willChange` and `didChange` arguments to name the hooks. In
  framework code (and now in test) these are always provided.
* Retain basically all the test coverage of array observers since they
  remain used by `ArrayProxy` internally (and through that interface, in
  Ember Data).

Co-authored-by: Matthew Beale <[email protected]>
(cherry picked from commit a9aedea)
@kategengler
Copy link
Member Author

This is done! Thank you to everybody who participated in deprecation removal <3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants