[MGNLGQL-47] Same-name types shouldn't be registered as GraphQL types Created: 17/Aug/20  Updated: 08/Sep/20  Resolved: 04/Sep/20

Status: Closed
Project: Magnolia GraphQL
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: GraphQL Phase 1
Sprint: HL & LD 10
Story Points: 8

 Description   
2020-08-06 10:32:25,856 ERROR info.magnolia.graphql.core.http.GraphQLServlet    : Failed to execute the GraphQL query
graphql.AssertException: All types within a GraphQL schema must have unique names. No two provided types may have the same name.
No provided type may have a name which conflicts with any built in types (including Scalar and Introspection types).
You have redefined the type 'Stats' from being a 'GraphQLObjectType' to a 'GraphQLObjectType'

AC:

  • Write validator that will prevent same-name type registration

Generated at Mon Feb 12 05:52:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.