Details
Assignee
Antranig BasmanAntranig BasmanReporter
Antranig BasmanAntranig BasmanComponents
Fix versions
Priority
Major
Details
Details
Assignee
Antranig Basman
Antranig BasmanReporter
Antranig Basman
Antranig BasmanComponents
Fix versions
Priority
Created January 8, 2021 at 4:13 PM
Updated November 2, 2021 at 12:59 PM
The problems with the defaults merging workflow are even more fundamental than reported in https://fluidproject.atlassian.net/browse/FLUID-6156#icft=FLUID-6156. Rather than just not being able to make expanded default options defaultible, we can't override any expanders listed in defaults.
The following setup:
fluid.defaults("hortis.leafletMap", { ... outerBounds: "@expand:fluid.geom.emptyBounds()", }); fluid.defaults("fluid.covidMap.map", { gradeNames: ["hortis.leafletMap", "hortis.streetmapTiles", "hortis.CSVLeafletMap", "hortis.conditionalTemplateRenderer"], .... outerBounds: { min: [-95.2, 41.6], max: [-74.3, 56.9] }, )}
ends up with the original expander being evaluated, since the merging algorithm produces a corrupt record with the (long-form) expander record plasted on top of the overriding value.
Yet another thing to fix when we regularise the expansion and merging pipeline for https://fluidproject.atlassian.net/browse/FLUID-5304#icft=FLUID-5304.