Share the task mutation GraphQL selection set

[coderabbitai]

Summary

Define a shared GraphQL fragment for the repeated nine-field selection set in the create-task and update-task documents.

Required changes

• Extract the common task selection set into a GraphQL fragment.
• Use the fragment in the create-task and update-task mutations.

Affected areas

• Create-task GraphQL document
• Update-task GraphQL document
• Shared GraphQL fragment

Acceptance criteria

• The repeated nine-field task selection set is defined once.
• Create and update mutations retain their current response fields.

Source

• Review comment: docs(readme): improve instructions #42 (comment)
• Pull request: docs(readme): improve instructions #42
• Requested by: @Alejandroq12

[coderabbitai]

Technical note

A fragment is a contract for one reusable selection set. Give it a domain name, such as TaskFields, and colocate it with the task GraphQL documents. Ensure the fragment type condition matches the returned task type. Regenerate or type-check generated client types after the change.

Reference: GraphQL: Fragments

[coderabbitai]

Engineering note

Use a fragment for a stable response shape that multiple operations require. Give it a domain-specific name and keep it close to the task GraphQL documents. Confirm generated types and both mutation responses still contain the required fields after extraction.

Read: GraphQL: Fragments