[MAGNOLIA-5148] Auto generated components are not always in same order Created: 03/Jul/13  Updated: 21/Aug/13  Resolved: 20/Aug/13

Status: Closed
Project: Magnolia
Component/s: rendering
Affects Version/s: 4.5, 5.0.2
Fix Version/s: 4.5.11, 5.0.3, 5.1

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relation
is related to MAGNOLIA-5239 Handling of autogeneratedComponents d... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Auto generated components are not always in same order. This is due to fact, that ConfiguredAutoGeneration holds content in HashMap which doesn't guarantee order of items.


Generated at Mon Feb 12 04:02:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.