-
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
Equals na comment #546
Equals na comment #546
Conversation
The logs complain about mising Also note you'll probably need to use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
The failure on CI is due to the following:
The issue is that Is that expected behavior? Till now, I've assumed In this case, since the code doesn't in fact parse:
I am surprised |
This is due to #560. |
I see... that means we have to keep If not, I think we'd have to do something like this in all XML-based linters:
pretty awkward IMO! |
I agree that this double check looks a bit weird. |
OK moved back to WIP, I'll update it once #609 is merged. |
OK this should be ready to go now. Passing locally. |
TIL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks!
Closes #545
Beyond just skipping usages which might be found in comments, I also took the opportunity to extend the logic of the linter:
NA == x
is now matched (before, it was justx == NA
; this came for free with the move to xpath)x != NA
is also matched. It would be trivial to extend this to other comparators (>|>=|<|<=
), but I wasn't sure that would gel with the name of the linter (not equals is similar enough I think)x\n==\nNA
(again, for free with the move to xpath).I also added a helper function for extracting
Lint
s from theirxml
nodes. This can likely be re-used in a few places.