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
Some SQLFluff failures are not resulting in an annotation. In most/all cases, it seems like the failure is straightforwardly corresponding to a single line, i.e. it's nothing crazy complicated and doesn't seem like it's only effecting edges cases.
For example:
== [collisions/2024-01-19_i0581_Collisions_red-light_camera_group/i0581_rlc_collision_statistics.sql]
FAIL
L: 26 | P: 1 | LT08 | Blank line expected but not found after CTE closing
| bracket. [layout.cte_newline]
The action fails, but it doesn't give any feedback as to why.
I don't know why this is happening. I haven't see much of a pattern to it yet.
The text was updated successfully, but these errors were encountered:
I think I was seeing these as single-line annotations in the human-readable output from SQLFluff, but in the github annotations file, they were actually multi-line.
Some SQLFluff failures are not resulting in an annotation. In most/all cases, it seems like the failure is straightforwardly corresponding to a single line, i.e. it's nothing crazy complicated and doesn't seem like it's only effecting edges cases.
For example:
The action fails, but it doesn't give any feedback as to why.
I don't know why this is happening. I haven't see much of a pattern to it yet.
The text was updated successfully, but these errors were encountered: