[MGNLREST-331] Order of nodes may break i18n results returned from the Delivery endpoint Created: 24/Sep/21  Updated: 23/Nov/21  Resolved: 22/Nov/21

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: 2.2.9
Fix Version/s: 2.2.10

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

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Sprint: HL & LD 39, HL & LD 40
Story Points: 3

 Description   

Steps to reproduce

  1. Create i18nized content (for example default and german)
  2. Go to JCR Browser and swap order of the i18nized nodes where language variant precedes original (put myNode_de before myNode)
  3. Request content via Postman or URL

Expected results

Single I18nized node is returned in the result set.

Actual results

Two i18nized nodes same with same name are returned in the result set.

Workaround

Fix order in the JCR.



 Comments   
Comment by Mikaël Geljić [ 10/Nov/21 ]

the pull request went to the services/rest fork! reopening so we merge this to the correct target repo, should be modules/rest.

Comment by Jaroslav Simak [ 10/Nov/21 ]

Oooops , nice catch mgeljic :bow:. jsarf i just re-created the PR to point to correct module, can you approve and merge?

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