Add forwardRef to CommitsAndReviewTab - #51251
Merged
Merged
Conversation
breville
approved these changes
Apr 13, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When doing some testing in Java Lab I noticed we were getting a forwardRef warning around the CommitsAndReviewTab. We started seeing these after the redux upgrade. The fix is to add a forwardRef to this component.
Testing story
Tested locally that the tab still works as expected. As far as I can tell, this warning warns of potential unexpected behavior, but I haven't been able to produce any weird behavior without the forwardRef.
PR Checklist: