Validate that reader aliases are unique in a fragment

isographlabs / isograph

The UI framework for teams that move fast — without breaking things.

MIT License

202 stars 9 forks source link

Closed rbalicki2 closed 4 months ago

rbalicki2 commented 4 months ago

There is no validation that fields in a given reader artifact do not share the same alias or field name. e.g. this should be invalid, but is allowed:

      nameWithOwner
      nameWithOwner: id

Also, the same field twice, with neither having an alias is allowed, but should be disallowed.
Also, multiple fields with a conflicting alias should be disallowed.