fix(View): Fix showOrientationAxes error #91
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
tamaynard
changed the title
|
@tamaynard Could you please add a better commit message describing the change and what issue it fixes? |
tamaynard
force-pushed
the
fix-orientation-axes
branch
2 times, most recently
from
16e758c to
460c3bd
Compare
…renderer and renderwindow are initialized
tamaynard
force-pushed
the
fix-orientation-axes
branch
from
460c3bd to
cb10ab3
Compare
|
I added an updated message, plus re-added the line adding the newly constructed renderer to renderwindow |
sankhesh
approved these changes
Dec 16, 2022
|
LGTM! |
github-actions bot
pushed a commit
that referenced
this pull request
Dec 19, 2022
fix(View): Fix showOrientationAxes error 0bd5eea
|
🎉 This PR is included in version 1.15.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Following up on #78