Skip to content

sr context: Create and Details page#2321

Open
r-vasquez wants to merge 6 commits intofe/sr-context-supportfrom
rv/sr-context-2
Open

sr context: Create and Details page#2321
r-vasquez wants to merge 6 commits intofe/sr-context-supportfrom
rv/sr-context-2

Conversation

@r-vasquez
Copy link
Contributor

@r-vasquez r-vasquez commented Mar 18, 2026

This PR adds the missing pieces of the Schema Registry context support. It now supports the Create and Details pages; both pages remain unchanged if the feature is not enabled.

It also features new UI components, such as the new combobox table view and the keyValue field.

Examples:

Schema Creation
image

Referencing other schemas:
image

Details page
image

- Pass selected context from schema-list to
  create page via context-aware route
- Pre-populate context and references when
  navigating from a named context
- Gate context route behind feature flag with
  "Not Supported" page when disabled
- Migrate schema-create to Registry components
  (Select, RadioGroup, ToggleGroup, Combobox,
  KeyValueField, Switch, Typography)
- Extract contextNameToId utility to unify
  context name-to-ID conversion across pages
- Deduplicate deriveContexts call in editor
When creating a schema in a named context with
references to default-context subjects, the
schema registry auto prexixes unqualified
references with the parent's context. Resulting
in non-existen lookups.

Now we explicitly qualify default context
references with `:.:`.

And, in the backend we were sending a request
to createSchema which makes additional API calls
and we were only interested in the ID as part of
the response, so we now just call register and get
the ID.
We want the user to understand that the qualified
subject name means that the first part `:...:` is
the context, so we grey-out the context name as we
do in the other pages.
@r-vasquez r-vasquez changed the title Rv/sr context 2 sr context: Create and Details page Mar 18, 2026
@r-vasquez r-vasquez marked this pull request as ready for review March 18, 2026 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant