fix(api): normalize API key labels - #101
Open
aiirvizionz wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Why
API key labels are shown back to users in account management. Without normalization, labels containing only whitespace or messy spacing can be stored and displayed as-is, making API key management harder to scan.
Tests
apps\web\node_modules\.bin\vitest.cmd run apps/web/lib/entitlements.test.tsNote:
pnpm --filter @aiornot/web test -- lib/entitlements.test.tsattempted to install dependencies first and stopped at pnpm's ignored-builds approval gate for esbuild/sharp/unrs-resolver, so I used the local Vitest binary after install populated node_modules.