field merging - field TYPES must not differ

[rivantsov]

Minor correction, Editorial.

[netlify]

✅ Deploy Preview for graphql-spec-draft ready!

Name	Link
🔨 Latest commit	d3f61c0
🔍 Latest deploy log	https://app.netlify.com/sites/graphql-spec-draft/deploys/63b72bd546c3060008946d7b
😎 Deploy Preview	https://deploy-preview-979--graphql-spec-draft.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[benjie]

This is not true; the field types do not have to be the same, they just have to be compatible. Please read http://spec.graphql.org/draft/#FieldsInSetCanMerge() carefully and consider fields with polymorphic types (unions and interfaces). The text as currently stated in the spec is, however, correct.

[rivantsov]

The text as currently stated in the spec is, however, correct.

so, "scalar values must not differ" - it is correct? which values? we are at early validation stage, we do not have any values yet. I thought it should say something about types; ok, maybe not require the exact same types, then pls help to formulate the proper short phrase describing 'type' requirements

[benjie]

You could change the word "values" to "types" I suppose.