Update fragment's definition in Learn-Queries.md
Updating the wording on how fragment should be used to nudge people towards a more scalable approach of using fragments to define data requirements.
Description
Even though the spec allows fragments to be used however people see fit, the document should nudge people towards a better usage pattern that scales well. In this case, attempt to describe them as composable pieces of data requirements used by UI or utility code. I hope this isn't controversial.
The committers listed above are authorized under a signed CLA.
- :white_check_mark: login: inlineblock / name: Dennis (497aa7b4270e92733a8c373ae487112ad4699299, bca76f98740b439ae6a1df5c2198b4ff4d7f1162)
:white_check_mark: graphql.github.io-source deploy preview ready
- Deploy preview
- Build logs · 2m build time
- Performance 57 :orange_circle: · Best Practices 92 :green_heart: · SEO 85 :orange_circle: — View full report
@benjie thank you for the review! I can do a follow PR to rename the fragment across the document.