[MGNLGQL-39] Support for content-types with special characters Created: 15/Jul/20  Updated: 15/Mar/21

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

Type: Improvement Priority: Neutral
Reporter: Robert Šiška Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLGQL-26 Content types with dash in name will ... Closed
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)
Epic Link: GraphQL Phase 2
Story Points: 2

 Description   

MGNLGQL-26 implemented name validator, but it doesn't convert invalid names (which are valid content-type names) as stated by Acceptance criteria. Since it's already merged, AC were moved to this ticket.

Copied from MGNLGQL-26:
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

TIMEBOX: 2pts
Investigate if we should convert special chars or just declare them invalid.


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