[MGNLGQL-3] GraphQL i18n Created: 13/May/20  Updated: 29/Jun/20  Resolved: 29/Jun/20

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5d
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)
Documentation update required:
Yes
Epic Link: GraphQL Phase 1
Sprint: HL & LD 4, HL & LD 5
Story Points: 5

 Description   

Timebox for investigation: 5 SP

User story:

As a developer I want the GraphQL endpoint to support returning one or more langauges, so I can handle multi language scenarios.

Notes:

Should behave similar to the delivery endpoint (unless the GraphQL spec specifies otherwise.)

Acceptance criteria:

  • By default the language specified by the browser is returned
  • Developer can request a specific language
  • Developer can request all languages


 Comments   
Comment by Christopher Zimmermann [ 16/Jun/20 ]

Removing requirement for all languages as there is no known convincing use-case.

Adding to a "under consideration" section on this page: https://wiki.magnolia-cms.com/display/TH2/GraphQL+Stories

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