[2024-03] Ensure use of "composite" term doesn't cause confusion in GraphQL.js

[benjie]

Check out wording in GraphQL.js to ensure this wording change can’t cause confusion and add non-normative note explaining composite referring to object/interface/union

• assignee(s): @JoviDeCroock
• source: https://github.com/graphql/graphql-wg/blob/2b81dcd0eb600e5cb96427ce5864ea5d07965b63/notes/2024/2024-03.md#call-for-reviews-5m-jovi

---

Note: Action Item issues are reviewed and closed during Working Group
meetings.

[benjie]

@JoviDeCroock Please reply to this so I can assign you.

[JoviDeCroock]

👋

[JoviDeCroock]

I double and triple checked but could not find confusion

[benjie]

The related PR was merged in June:

• chore: add clarifying note for composite and expand term graphql-spec#1078

[JoviDeCroock]

For reference https://github.com/graphql/graphql-js/blob/48afd37a48d37f6d3342b959e8cb34e1ecbfeffb/src/type/definition.ts#L293 - we could go further in this and remove comments as well but I don't particularly mind the overarching term in an implementation.