Closed nikorev closed 11 months ago
To note, for the windows_registry_key
object in AF-125, I moved the validation under the Vaidate links section of validateNode()
to prevent checking over the object multiple times. This could technically be done for this branch/check too since we're also checking based on the node.template.id
, but since all of these objects only have a single property in the node.props.value
for loop, we aren't iterating more than once. I'll keep it where it is for now.
Additional clarification: The for-loop shown in the screenshot will only run once for any of the ipv4/ipv6/mac address nodes since they only contain a single property
In contrast with the AF-125 (windows registry) branch, this for loop would iterate 4x for each of the properties (key, values, date modified, # of subkeys); this is why the validation for windows registry keys is in a slightly different place.
SonarCloud Quality Gate failed.
0 Bugs
0 Vulnerabilities
0 Security Hotspots
17 Code Smells
No Coverage information
0.0% Duplication
Catch issues before they fail your Quality Gate with our IDE extension
SonarLint
Using regexes found in