fix!: remove *BufferGeometry type aliases #2443
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
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 3f8b6cb:
|
joshuaellis
approved these changes
Aug 17, 2022
|
They'll still work, emitting a warning when constructed. However, they will be removed entirely in 10 releases, so they're effectively depreciated as far as library authors are concerned. I've already updated Drei and three-stdlib, this would be more troublesome in user space. |
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.
r144 deprecates usage of
BoxBufferGeometryaliases in favor ofBufferGeometry. As per three deprecation policy, these will be completely removed in r154, so preferring to remove any references to them now. In JS-land, this would emit a warning.