Skip to content
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

Closed

Conversation

ziegenberg
Copy link
Member

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.

Copy link
Member

@Arnei Arnei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to break whatever arcane magic the WizardStepper is using. In the image below I'm in the "source" step, but the WizardStepper believes me to be in the "asset upload" step.

Bildschirmfoto vom 2024-05-14 13-57-06

@Arnei Arnei added the type:bug Something isn't working label May 16, 2024
Copy link
Contributor

This pull request has conflicts ☹
Please resolve those so we can review the pull request.
Thanks.

@ziegenberg ziegenberg force-pushed the fix-unique-key-issue-in-wizzard branch from aa02f60 to c191574 Compare May 21, 2024 16:19
@ziegenberg ziegenberg closed this May 21, 2024
@ziegenberg ziegenberg force-pushed the fix-unique-key-issue-in-wizzard branch from c191574 to 4e8106c Compare May 21, 2024 16:29
@ziegenberg ziegenberg reopened this May 21, 2024
@ziegenberg ziegenberg force-pushed the fix-unique-key-issue-in-wizzard branch from 7cd629a to 41acd80 Compare May 21, 2024 16:52
Copy link
Contributor

This pull request has conflicts ☹
Please resolve those so we can review the pull request.
Thanks.

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]>
@ziegenberg ziegenberg force-pushed the fix-unique-key-issue-in-wizzard branch from 41acd80 to 0a159d9 Compare May 24, 2024 15:45
@ziegenberg
Copy link
Member Author

Rebased.

@ziegenberg ziegenberg marked this pull request as draft May 24, 2024 21:02
Copy link
Contributor

github-actions bot commented Jun 4, 2024

This pull request has conflicts ☹
Please resolve those so we can review the pull request.
Thanks.

@Arnei
Copy link
Member

Arnei commented Jul 11, 2024

Can't reproduce the web console warning anymore, so we can probably close this. @ziegenberg, what say you?

@ziegenberg
Copy link
Member Author

Yeah, it was fixed in another way. So, closing it is.

@ziegenberg ziegenberg closed this Jul 11, 2024
@ziegenberg ziegenberg deleted the fix-unique-key-issue-in-wizzard branch July 11, 2024 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:conflicts type:bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants