How should you properly structure GraphQL fragments to genuinely share a common set of fields consistently across several separate different queries, keeping your overall GraphQL codebase genuinely more maintainable as it steadily grows?

A GraphQL fragment lets you properly define a genuinely reusable named set of fields exactly once, then conveniently include that exact same defined fragment within several genuinely separate different queries or mutations, meaning if a specific commonly used shared field, such as a standard user profile's own particular set of displayed fields, ever genuinely needs to change, you only ever actually need to update that one single shared fragment definition itself, rather than needing to separately hunt down and properly update every single individual query throughout your entire codebase that happened to individually include that exact same specific repeated set of fields.

fragment UserFields on User {
  id
  name
  email
}

query {
  currentUser { ...UserFields }
  post(id: "1") { author { ...UserFields } }
}