feat(ui): add API key visibility toggle #13110
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
AaronClaes requested review from AlessioGr, JarrodMFlesch and jacobsfletch as code owners 
JarrodMFlesch approved these changes Jul 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
What?
I added a visibility toggle to the API key field.
Key hidden:
Key visible:
Why?
When visiting a collection item that has an API key enabled, the API key is exposed and openly visible.
This can cause unexpected leakage of the key.
Current field:
How?
I added a
showKeystate to the component, which can be toggled.The toggle is placed next to the input field, following the same UX/UI pattern as the "Add new" button for the relationship field.