refactor(frontend): Make the secrets table styling consistent. #9628
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.
End-user friendly description of the problem this fixes or functionality this introduces.
🔍 Description
The visual styling of the Secrets table differs from that of the API Keys table, leading to inconsistency in the UI. Aligning their design will improve overall cohesiveness and user experience.
The Secrets table currently uses a different styling approach compared to the API Keys table, which creates a visual mismatch across similar components.
✅ Expected Behavior
❌ Current Behavior
🔁 Steps to Reproduce
📹 Additional Context
A video demonstrating the issue is available below:
issue.mov
Summarize what the PR does, explaining any non-trivial design decisions.
Update the Secrets table to match the visual style and layout of the API Keys table (e.g., typography, spacing, border styles, icons, etc.).
A video demonstrating the output is available below:
output.mov
Link of any specific issues this addresses:
Resolves #9627