-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False positives with nonportable_path_linter
for text that contains "/"?
#468
Comments
I think a way out here is to add a parameter like Whether to allow spaces / parentheses is more of an edge case, it could be a second parameter? Otherwise it's hard to both (1) allow spaces/parentheses in paths and (2) skip edge cases like |
it is pretty common to have / in quoted string such as time zones "America/New_York". |
It seems that most/all text that uses the character "/" is considered a file path by
nonportable_path_linter
.In cases when "/" is used for reasons other than as a file path separator and, consequently, "file.path" is not used,
nonportable_path_linter
marks the code as in need of linting. Is the intent of this linter that all such uses be removed or is the linter currently too greedy in determining what constitutes a file path? Thanks!Example:
Output of example code:
The text was updated successfully, but these errors were encountered: