[MAGNOLIA-8092] More than 50 aliases in a YAML file breaks parsing Created: 12/May/21 Updated: 04/Jul/22 Resolved: 16/Feb/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 6.2.8 |
| Fix Version/s: | 6.2.17 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Chris Jennings | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 0.25d | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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
|
||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | Support | ||||||||||||||||
| Sprint: | Global Maintenance 3, Global Maintenance 4, DevX 1, DevX 2, DevX 3, DevX 4 | ||||||||||||||||
| Story Points: | 5 | ||||||||||||||||
| Team: | |||||||||||||||||
| Description |
Steps to reproduce
Expected results
Actual results
Workaround
Development notes
|
| Comments |
| Comment by Richard Gange [ 14/May/21 ] |
|
Looks like there is a setter available. I guess we need to provide some way to set it. Maybe our properties file? |
| Comment by Richard Gange [ 20/Dec/21 ] |
|
Just for the record there is a new property maxAliasesForCollectionsInYaml on the config node of the configuration module. |
| Comment by Aleksandr Pchelintcev [ 21/Dec/21 ] |
|
The proposed fix may provide the correct configuration, but deliberately turning YamlReader from a formerly fairly standalone utility into something that depends on Magnolia module registry and presence of ConfigModule in particular complicates a lot of things. Especially unit tests that involve YamlReader. |
| Comment by Robert Šiška [ 01/Feb/22 ] |
|
akhamis It is supposed to be /modules/config/config/yamlReaderConfiguration/maxAliasesForCollectionsInYaml |
| Comment by Roman Kovařík [ 08/Feb/22 ] |
|
What's the reason to put a new config into JCR? The configuration app as it is will be gone soon in favour of YAML configs. |