-
Notifications
You must be signed in to change notification settings - Fork 4.4k
UI: Add assertion to FormField
for @attr.name and @model args
#30788
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: |
FormField
for @attr.name and @model args
@hellobontempo I think we've reached a consensus that this is the way to go. Do you mind doing also the second part in this PR, which is to remove the guards too? In this way there is a single ticket and it's easier to track the changes and why. Thanks |
Yes! Absolutely. I'm a little busy feature testing until code freeze next Friday but I can update afterward. Feel free to takeover the PR/branch if this is blocking you until then 😄 |
3486983
to
e5bbee0
Compare
…grated HDS components
…ult into ui/add-form-field-assertion
Build Results: |
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.
Nice! 👍
* test assertion for form fields * resuse const cars * add tests * remove conditionals for attr.name * link jira VAULT-36640 * test assertion for form fields * resuse const cars * add tests * remove conditionals for attr.name * [UI] removed guard for `this.hideLabel` and `this.labelString` for migrated HDS components * reverty copy pasta --------- Co-authored-by: Cristiano Rastelli <[email protected]>
…DS block (#30771) * [UI] Updated `FormField` to use `Hds::Form::Checkbox` for `type/editType=boolean` (#34798) * [UI] Updated `FormField` tests for `type/editType=boolean` (#34798) * [UI] Fixed failing test cases from `FormField` `boolean` updates (#34798) * [UI] fixes raised in PR review (#34798) * removed `this.labelString` guard per agreement see #30788 * [UI] replaced `assert.ok` with `assert.true` per code review suggestion * updated `isHdsFormField` logic to reflect more accurately inital “logic” flow in the `form-field.hbs` template file for context: https://hashicorp.slack.com/archives/C05DGFEBCP2/p1751023770911809 * fixed test that was erroneously changed in previous PR due to an undetected bug the previous code was generating a `checkbox` instead of a `toggleButton` it’s now been fixed (see previous commit) * Update ui/lib/core/addon/components/form-field.hbs Co-authored-by: claire bontempo <[email protected]> --------- Co-authored-by: claire bontempo <[email protected]>
Description
✅ enterprise tests pass
VAULT-36640
@attr.name
key and@model
arghideLabel
guard and thethis.labelString
guard from the migrated HDS components (per decision documented here)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.