-
Notifications
You must be signed in to change notification settings - Fork 23
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
Fix unique key issue in WizzardStepper #386
Fix unique key issue in WizzardStepper #386
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request has conflicts ☹ |
aa02f60
to
c191574
Compare
c191574
to
4e8106c
Compare
7cd629a
to
41acd80
Compare
This pull request has conflicts ☹ |
Fixes a web console complaint about missing unique keys in the WizzardSteppers. I deem using .filter() a nicer solution than a ternary operator that checks if the hidden property of the current label object is false and rendering an empty fragment. This is probably also what made the console unhappy. Signed-off-by: Daniel Ziegenberg <[email protected]>
41acd80
to
0a159d9
Compare
Rebased. |
This pull request has conflicts ☹ |
Can't reproduce the web console warning anymore, so we can probably close this. @ziegenberg, what say you? |
Yeah, it was fixed in another way. So, closing it is. |
Fixes a web console complaint about missing unique keys in the WizzardSteppers. I deem using .filter() a nicer solution than a ternary operator that checks if the hidden property of the current label object is false and rendering an empty fragment. This is probably also what made the console unhappy.