UX Changes to the API Keys Screens #1260
Merged
Conversation
This file contains 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
…eys and Warning the user before deletion.
# Conflicts: # packages/ui/src/views/apikey/index.js
|
small update on ui: |
HenryHengZJ
approved these changes
Nov 23, 2023
hemati
pushed a commit
to hemati/Flowise
that referenced
this pull request
Dec 27, 2023
…tials UX Changes to the API Keys Screens
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the API Keys Screen to show the number of chatflows associated with each key and allows the user to view the flow details. The warning message is also updated to ensure that the user does not accidentally delete the key.