-
Notifications
You must be signed in to change notification settings - Fork 5
feat: migrate go-sdk #71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
freeznet
wants to merge
43
commits into
main
Choose a base branch
from
freeznet/migrate-sdk
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Record go-sdk dependency and update module metadata for migration.
Add jsonschema-go helpers and tests for tool input/output schemas.
Keep legacy registration while aligning builder schema and handlers with go-sdk typing.
Add go-sdk schema/handler for Kafka produce and keep legacy adapter for mark3labs server compatibility.
Use go-sdk tool definitions/handlers and add schema registry schema coverage.
Why: align Pulsar admin topic tooling with the go-sdk handler and schema pipeline while preserving legacy server support.
Add go-sdk builders with schema generation, legacy adapters, and tests.
Use the go-sdk tool builder with jsonschema input, add a legacy adapter for the mark3labs server, and cover schema expectations with tests.
Migrate topic policy tool to the go-sdk with a legacy adapter and schema tests to preserve behavior parity.
Add go-sdk request/session accessors and typed-nil guard for context-based retrieval.
Ensure panic recovery matches legacy tool handler messages and runs without a logger.
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.
No description provided.