Conversation
Routes for managing admin api keys, display them on keys page
Allow bulk prop parsing to upsert
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
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.
Admin API keys
AdminApiKeyentity with its own schema (keyEnding, separate scopes) and full CRUD API surface (createAdminApiKey,updateAdminApiKey,deleteAdminApiKey,useAdminApiKeys)Terminology alignment
Bulk props import merge behaviour
PropsEditorto correctly merge pasted bulk props into existing props by key (updating in-place) instead of appending duplicates, avoiding key collisions when re-pastingMinor styling correction
RadioGroupoption label margin fromml-1toml-2for consistent spacing