-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
UI/fix kmip role form #13585
UI/fix kmip role form #13585
Conversation
…leRow invocations
@@ -1,4 +1,4 @@ | |||
<InfoTableRow @label="Name" @value={{@model.name}} @data-test-alias-name={{true}} /> | |||
<InfoTableRow @label="Name" @value={{@model.name}} data-test-alias-name={{true}} /> |
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.
Curious how that @data
.... got in there!
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.
Probably an upgrade maybe even back to the big one in 1.7
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.
I think it was the latest ember upgrade. I considered find-replacing all the @data-test
instances, but we have a few cases where it looks like they're actually supposed to work that way (eg. ToolbarSecretLink 😱)
</InfoTableRow>`); | ||
|
||
let block = document.querySelector('[data-test-value-div]').textContent.trim(); | ||
assert.equal(block, 'Block content is here', 'renders block passed through'); | ||
}); | ||
|
||
test('Row renders when block content even if alwaysRender = false', async function (assert) { |
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.
Thank you for adding test coverage!
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 work!
I was wondering how the layout thing was going to work when glimmerizing addon components. Looks like the template has to be moved along side the component file and it just works? |
* Fix info-table-row not rendering if alwaysRender=false and only block content present * use defaultFields for form and nonOperationFields for adapter * WIP: Move info table row template to addon component dir * Refactor InfoTableRow to glimmer component * Add changelog * passthrough attributes, change @data-test-x to data-test-x on InfoTableRow invocations
Before this fix, there was a bug where creating a KMIP role did not save any non-operator keys. There was also an issue where TLS info was not displayed on the show details page, due to an issue in InfoTableRow. As part of this work, I glimmerized InfoTableRow Component and added tests for various scenarios.
Before (key bits value does not save)
After