fix: create_topic returns only topic id to avoid deserialization errors#495
Merged
fix: create_topic returns only topic id to avoid deserialization errors#495
Conversation
The POST /v1/content/topics response may omit fields like `license`, causing deserialization failures when mapping to OwnedTopic. Simplify create_topic to only parse item.id from the response across all bindings (Rust, blocking, Python sync/async, Node.js, Java, C). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
huacnlee
force-pushed
the
fix/create-topic-return-id
branch
from
a5815c0 to
060b9a0
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.
Summary
POST /v1/content/topicsresponse may omit fields likelicense, causingmissing field 'license'deserialization errors when mapping toOwnedTopiccreate_topicto only parseitem.idfrom the response, returningStringinstead ofOwnedTopicTest plan
longbridge create-topic --type article ...and verify it returns the topic ID without deserialization errors🤖 Generated with Claude Code