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

Feat/use unique id to have valid label for attributes page 4088 #3401

Conversation

dylanBetty
Copy link
Collaborator

No description provided.

jrquak and others added 9 commits March 5, 2024 13:08
…belongsto-support-PAGE-4109

feat: enabled resetting value of autocomplete
# [2.185.0](v2.184.0...v2.185.0) (2024-03-11)

### Features

* enabled resetting value of autocomplete ([576a75b](576a75b))
…alues-PAGE-4132

Feat/laod hasmany pagevar values page 4132
# [2.186.0](v2.185.0...v2.186.0) (2024-03-19)

### Bug Fixes

* no value fix for habtm ([67063ae](67063ae))
* prevent empty values beeing pushed ([5f21d53](5f21d53))

### Features

* added pagvar hasmany support ([7b05fca](7b05fca))
…mponent so that it adheres to the WCAG standards
@@ -268,6 +269,7 @@
>
{labelText && !hideLabel && (
<InputLabel
htmlFor={id}
Copy link
Collaborator

Choose a reason for hiding this comment

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

ComponentID is shown in the snapshot as secret-id-do-not-use, but we do use it here.

I do not know exactly how valid the 'do not use'-warning is, but maybe we should take it seriously.

Alternative: make a page-wide counter-helper, which return a unique, incremented counter each time it is called. We can use the result of that counter, with a prefix, to generate unique for-ids.

Pro: this setup may also help for the iterated input-components.

@dylanBetty dylanBetty closed this Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants