Rename registry to schema registry in handlers and docs#3
Closed
gitrus wants to merge 1 commit into
Closed
Conversation
gitrus
force-pushed
the
claude/rename-registry-schema-5QF72
branch
from
eed7931 to
af9c8c8
Compare
gitrus
force-pushed
the
claude/rename-registry-schema-5QF72
branch
from
af9c8c8 to
9387c68
Compare
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.
Renames internal/httpapi/registry -> internal/httpapi/schemaregistry
and docs/REGISTRY_HANDLERS.md -> docs/SCHEMA_REGISTRY_HANDLERS.md to
match the component's actual responsibility: serving entry-type schemas.
Public URL paths (/v1/registry, /v1/registry/{type}) are kept as-is to
avoid breaking clients.