Affects Version/s: None
Fix Version/s: None
In the following detected situations settings transforms are filtered out when they shouldn't:
Due to not having any dependency in form of "inputPaths" this settings are optimized out. See https://github.com/GPII/universal/blob/master/gpii/node_modules/transformer/src/js/Transformer.js#L76.
The example here is the setting:
when this settings is targeted with the payload:
The following settings path are inferred:
The base path:
is wrongly inferred to be a combination of two settings:
Due to this, when trying to access the setting this operation will never succeed:
Because the "supportedSettingsPath" will never match the string in the "actualSettingPaths".