fix: Remove company field from conversation schema in v2.15#426
Open
markdennis22 wants to merge 1 commit intomainfrom
Open
fix: Remove company field from conversation schema in v2.15#426markdennis22 wants to merge 1 commit intomainfrom
markdennis22 wants to merge 1 commit intomainfrom
Conversation
The company field on conversations is only available in the Unstable API version. It was incorrectly included in the v2.15 spec. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
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.
Why?
A customer reported that
company_idappears in the Search Conversations response docs for stable API versions, but the API only returns it for the Unstable version. Thecompanyfield was incorrectly added to theconversationandconversation_list_itemschemas in the v2.15 spec.How?
Removes the
companyproperty (4 lines each) from both theconversationandconversation_list_itemschemas in the v2.15 spec. The Unstable spec is unchanged — the field is correct there.Generated with Claude Code