[MAGNOLIA-6719] Map2Bean should always interpret map keys as Strings Created: 13/Jul/16  Updated: 19/May/22  Resolved: 19/May/22

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

Type: Bug Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLSITE-67 Image variations with integer names 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
Date of First Response:

 Description   

At least in the case of imaging variations in a theme, and probably in other cases, when a key in a YAML file is interpretable as an integer (such as 5 or 256 or 400) Map2Bean stores it as an integer instead of a String. This can cause problems in other code which attempts to match a string value to find a specific item in a map.

For example, this problem occurs when the variation resolver takes the string name of an imaging variation, such as "400" and tries to find a matching imaging variation in a theme - currently it fails because the key in the YAML definition was interpreted as an integer.

Note that definitions provided by JCR with numbers as key work correctly. This is used in the travel-demo-theme.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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