-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[VAULT-34742] UI: move the generic select block in FormField under the HDS block
#29960
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
Conversation
|
CI Results: |
|
Build Results: |
…generic `select` use case (#34742)
…he `isHdsField` block (#34742)
f42f859 to
2ad0d02
Compare
Monkeychip
left a comment
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.
Looks great. Left some comments but one is more for me, and the other is for when you move to checkboxes.
@Monkeychip I replied to both :) |
…r the HDS block (#29960) * [UI] updated logic in `isHdsFormField` of `FormField` to include the generic `select` use case (#34742) * [UI] moved template logic for generic `select` in `FormField` under the `isHdsField` block (#34742)
Description
What does this PR do?
isHdsFormFieldofFormFieldto include the genericselectuse caseselectinFormFieldunder theisHdsFieldblockJira ticket: https://hashicorp.atlassian.net/browse/VAULT-34742
Diffs
A few examples of before vs after:
Before:

After:

Before:

After:

👉 In this case the
@helpTextinstead of being hidden behind a tooltip, is exposed as field's helper text (better for accessibility)TODO only if you're a HashiCorp employee
backport/label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x, but older release branches will bebackport/ent/x.x.x+ent.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.