The current implementation uses the defaultsDeep function of loadash to implement the precedence principles of the viewer. It starts from the user data and replaces undefined fields with the metadata and then the defaults..
The new implementation must reverse the strategy. We want to replace the lodash defaultsDeep function with merge and start with the default config and use the metadata config to overwrite the fields in the default config to replace them with the metadata values and then do the same to replace the default+metadata fields using the user config.
Is there an existing issue for this?
Who request this Feature
Team
User Story
The current implementation uses the defaultsDeep function of loadash to implement the precedence principles of the viewer. It starts from the user data and replaces undefined fields with the metadata and then the defaults..
The new implementation must reverse the strategy. We want to replace the lodash defaultsDeep function with merge and start with the default config and use the metadata config to overwrite the fields in the default config to replace them with the metadata values and then do the same to replace the default+metadata fields using the user config.
Implementation UI
No response