deprecate @vx/boxplot
#561
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
one possible issue is with the docs, I'm not sure if we run the docs script while in the TS/JS limbo, and currently most of the docs |
|
going to merge this guy because some of the lint errors it fixes are failing the build in other PRs. Can follow up with any issues in another PR. |
|
noting successful deprecation on
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
💥 Breaking Changes
This PR closes #560 and removes all references to
@vx/boxplotwhose functionality is duplicated in the@vx/statspackage and has confused some users (e.g., #412)After this is merged I will add a deprecation warning to npm:
npm deprecate @vx/boxplot "@vx/boxplot has been deprecated in favor of @vx/stats"@hshoff @conglei