Skip to content

chore(breaking): Remove deprecated APIs #179

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

Closed
wants to merge 3 commits into from

Conversation

Esemesek
Copy link
Collaborator

@Esemesek Esemesek commented May 28, 2019

Summary

Remove deprecated APIs for 2.0 release.
Things removed:

  • shallow API
  • *ByProps queries
  • *ByType queries
  • *ByName queries

TODO:

  • - Update documentation

Test plan

Tests passing.

@Esemesek Esemesek mentioned this pull request May 28, 2019
10 tasks
@thymikee thymikee changed the title Remove deprecated API chore(breaking): Remove deprecated APIs May 28, 2019
@thymikee
Copy link
Member

Let's hold off with merging for a bit. I'd like to release a11y matchers and maybe some other improvements, and remove those just before 2.0

@thymikee thymikee added this to the 2.0 milestone May 28, 2019
Copy link
Member

@thymikee thymikee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make it easier for people to migrate by following what React does:

  • add a notice about deprecation and alias unsafe queries with UNSAFE_ prefix in 1.x
  • remove non-prefixed unsafe queries in 2.0, leave UNSAFE_ ones with either no or different deprecation message (yet to be decided)

Also, let's exclude shallow from this PR. I'd like to move it to another package before removing it and also provide a deprecation notice in a separate PR.

@thymikee thymikee closed this Mar 18, 2020
@thymikee thymikee deleted the remove-deprecated-api branch March 18, 2020 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants