feat(linear): expose issue priority and timestamps in JSON output - #275
Merged
Merged
Conversation
Add priority (priority, priority_label, priority_sort_order) and timestamps (created_at, updated_at) to Issue and Comment resources so they are included in --output json for all commands. - Extend @issue_fields GraphQL selection with priority fields - Add five new attributes to LinearCli.Linear.Issue - Extract new fields in Issue.from_map/1 - Add created_at/updated_at to LinearCli.Linear.Comment (already in GraphQL selection via base_fields/0, but discarded until now) - Extract timestamps in Comment.from_map/1 - Update ash-domain-erd.adoc per maintenance contract Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Update issue_map/1 and comment_created/0 test fixtures with priority and timestamp fields matching the new GraphQL response shape - Add from_map/1 round-trip tests in issue_test and comment_test - Add --output json snapshot tests for issue list and issue view - Add Display.show/2 JSON tests for priority=0 preservation and snake_case field name stability Co-Authored-By: Claude Sonnet 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
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
priority,priority_label,priority_sort_order,created_at,updated_atattributes toLinearCli.Linear.Issue; extend@issue_fieldsGraphQL selection with the three priority fields (timestamps were already selected but discarded)created_at,updated_atattributes toLinearCli.Linear.Comment; extract them infrom_map/1(already inbase_fields/0GraphQL selection, but previously dropped)Display.to_plain/1generic struct-to-map converter — no serialization-specific code neededdocuments/ash-domain-erd.adocper the maintenance contractTest plan
from_map/1round-trip tests: priority values (0.0 and non-zero) and timestamps survive the GraphQL response → struct conversion for both Issue and Commentpriority,priorityLabel,prioritySortOrder,createdAt,updatedAtlc issue list --output jsonincludes all new fields; priority=0.0 preserved as real valuelc issue view --output jsonincludes all new fields on the issue and on nested commentsDisplay.show/2JSON output: field-name stability (snake_case, not camelCase), priority=0 preservation, comment timestamp nestingCloses EXT-64
🤖 Generated with Claude Code