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
Describe the bug
The path used to check applies to regexes is based on the relative path rather than the absolute path if the user provides a relative path for the source files argument.
To Reproduce
Steps to reproduce the behavior:
Run ApplicationInspector analyze -s relative/path with a file regex for a custom rule
Set a breakpoint in GetRulesByFileName in RuleProcessor.cs
Observe the value of the filename argument
Expected behavior
Paths should always be absolute internally even if the user initially provided a relative path. See also #588
The text was updated successfully, but these errors were encountered:
…analysis (#590)
* Fix#589
Convert user provided relative paths into absolute paths before scanning for consistent file name regex behavior in rules.
* Also use absolute path in error message
Describe the bug
The path used to check applies to regexes is based on the relative path rather than the absolute path if the user provides a relative path for the source files argument.
To Reproduce
Steps to reproduce the behavior:
analyze -s relative/path
with a file regex for a custom ruleGetRulesByFileName
inRuleProcessor.cs
filename
argumentExpected behavior
Paths should always be absolute internally even if the user initially provided a relative path. See also #588
The text was updated successfully, but these errors were encountered: