[MGNLGQL-26] Content types with dash in name will fail to convert into GraphQL Schema Created: 18/Jun/20  Updated: 15/Jul/20  Resolved: 02/Jul/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: 0d
Time Spent: 0.5d
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLGQL-39 Support for content-types with specia... Open
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 6, HL & LD 7
Story Points: 1

 Description   

GraphQL names must match following pattern:

/[_A-Za-z][_0-9A-Za-z]*/

Apart from this, names cannot also contain following characters:

! $ ( ) ... : = @ [ ] { | }

See also GraphQL Specification here.
 
Please make sure to test that all characters, that are not allowed by the GraphQL specification, are replaced.

Acceptance criteria:

  • Ensure that GraphQL names are converted into valid names – replace dashes with camelCase format

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