Update conversation assignee_id fields from null to 0#458
Draft
VarshSuresh wants to merge 1 commit intomainfrom
Draft
Update conversation assignee_id fields from null to 0#458VarshSuresh wants to merge 1 commit intomainfrom
VarshSuresh wants to merge 1 commit intomainfrom
Conversation
Removes nullable: true from conversation schemas, updates descriptions from "return null" to "return 0", and sets a subset of response examples to 0 so developers see both assigned and unassigned states. Applied across all versions (2.7-2.15 + Preview). Ticket schemas are untouched. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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?
Towards
The API returns
0(notnull) for unassignedadmin_assignee_idandteam_assignee_idin conversation responses. The docs currently document these fields asnullable: truewith descriptions saying "return null", which is inaccurate.How?
Removes
nullable: truefrom conversation schemas, updates descriptions from "return null" to "return 0", and sets a random subset of response examples to0so developers see both assigned and unassigned states. Applied across all versions (@2.7–@2.15 + @Preview). Ticket schemas are untouched.Generated with Claude Code