You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue is identified on a case in License comparison, when one of the licenses ("Logging Service") had an extra sub-dictionary ("custom") and randomly occurred since properties are checked at the lowest level in json and a random key is checked within the next level whether it's dictionary or not to identify if we are at the lowest level in order to process the passed properties. When the check is done on the "custom" key, it went further on the nested dict and produced a diff even it was set to skip serial and issued elements.
See following example:
Requested config: ["!serial", "!issued"]
Instead of checking if we are at the lowest level in order to process the passed properties (requested configuration), we can check if these exist on any level we are parsing, so the requested configuration can be applied on any level. This will require ignoring non-relevant requested configurations for a level on ConfigParser.
The text was updated successfully, but these errors were encountered:
Describe the bug
Issue is identified on a case in License comparison, when one of the licenses ("Logging Service") had an extra sub-dictionary ("custom") and randomly occurred since properties are checked at the lowest level in json and a random key is checked within the next level whether it's dictionary or not to identify if we are at the lowest level in order to process the passed properties. When the check is done on the "custom" key, it went further on the nested dict and produced a diff even it was set to skip serial and issued elements.
See following example:
Requested config:
["!serial", "!issued"]
Left side dictionary:
Right side dictionary:
Possible solution
Instead of checking if we are at the lowest level in order to process the passed properties (requested configuration), we can check if these exist on any level we are parsing, so the requested configuration can be applied on any level. This will require ignoring non-relevant requested configurations for a level on ConfigParser.
The text was updated successfully, but these errors were encountered: