-
Notifications
You must be signed in to change notification settings - Fork 4.4k
[VAULT-34216] UI: Namespace picker feature branch #30490
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: |
793e82f
to
b401229
Compare
Build Results: |
UP = 'ArrowUp', | ||
RIGHT = 'ArrowRight', | ||
DOWN = 'ArrowDown', | ||
T = 'F5', |
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.
Why does T
map to F5
?
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.
That's a good question!! I was replacing these keys one-for-one from key-codes.js
. In the deprecated key-codes
file, the T
key is mapped to key code 116
, which is F5
. But I'm not sure why they used T
instead of F5
as the key. It looks like there are currently no references to the T
key-code
... so I've just pushed a commit to removed all unused key code props. Thanks for catching this Lane!
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.
Sounds good! I wasn't sure where these were all from, and that once seemed a little opaque, so good follow-up!
ui/lib/core/addon/utils/key-codes.js
Outdated
DOWN: 40, | ||
T: 116, | ||
BACKSPACE: 8, |
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.
🗒️ Note: removing unused key codes
…ponent (#30068) * [VAULT-34482] UI: Update Namespace Picker to use HDS Super Select component * changelog updates * update jsdoc * update classname * update test comment * remove unnecessary label attribute * move hbs file to components directory alongside js file * fix replication test * undo changes to replication test * test update
…pace count label (#30183) * [VAULT-35046] Show namespace count label; use Hds::Dropdown instead of Hds::Superselect * address misc pr comments * update tests * address PR comment * Update ui/app/components/namespace-picker.hbs Co-authored-by: claire bontempo <68122737+hellobontempo@users.noreply.github.com> * Update ui/app/components/namespace-picker.hbs Co-authored-by: claire bontempo <68122737+hellobontempo@users.noreply.github.com> * address PR comments: update tests * use getter for namespace label --------- Co-authored-by: claire bontempo <68122737+hellobontempo@users.noreply.github.com>
…30433) * [VAULT-34483] UI: implement front-end pagination via infinite scroll * remove unnecessary height definition * fix test: Integration | Component | sidebar-frame: it should render namespace picker in sidebar footer * update comment * move visibleNamespaceOptions into a getter so that it updates when search input is cleared * handle edge case: display current namespace when no other namespaces listed
* [VAULT-35780] address TODOs * wrap manage & refresh buttons in Hds::ButtonSet * fix failing integration tests * remove unnecessary import mirage * fix undefined * fix flaky tests * styling updates * don't show search help text when there are no namespaces matching the search criteria
0c7ed48
to
5606b59
Compare
main
❗Description
Hds::Dropdown
componentjs
tots
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.