-
Notifications
You must be signed in to change notification settings - Fork 36
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 positive on F1 rule with a derived table #32
Comments
FYI, I started working on this for about 30 minutes, but I'm overlooking something really obvious and am failing to correctly set up a failing test so far. Putting the link here for reference, but I'll get back to this later: |
👋🏼 I'm experiencing this false positive as well when I use the same |
Last time I looked at this, I wasn't able to correctly set up a failing test. This time I've taken a look at the F1 code and have an idea where the bug may be.. I won't be able to work on code changes until likely next week, so I'm commenting my findings for now: The code that should handle ignoring However, the issue seems to be even before that, in the regex, which seems to be way too permissive in terms of what characters it captures (i.e. it will capture the spaces, equal signs, and remainder of the condition as though it were part of the reference) https://github.com/looker-open-source/look-at-me-sideways/blob/master/rules/f1.js#L47 Also, I should do something to look for multiple liquid tags within the block. Currently, it doesn't seem to be a global match or otherwise loop to catch multiple instances of liquid. |
Btw, @tstodden - In the short-term, if you're not yet adding an exemption to avoid this, I would recommend that as a temporary workaround. Thanks for the additional bug report! |
LAMS is reporting a false positive on the F1 rule for a derived table using parameters.
Detailed error:
linkback references another view, if linkback_type, via {% if linkback_type._parameter_value == "Client" %}
The full dimension code is:
The text was updated successfully, but these errors were encountered: