4 Commits

Author	SHA1	Message	Date
Coacher	0ef2c455ee	Properly handle optional end_line_no/end_line_pos in sqlfluff (#4867) ... end_line_no/end_line_pos are optional. Example SQL: `SELECT NULL FROM {{ a_jinja_templated_table }};` `sqlfluff lint --dialect ansi --format json` gives the following error among others: ``` {"start_line_no": 1, "start_line_pos": 21, "code": "TMP", "description": "Undefined jinja template variable: 'a_jinja_templated_table'", "name": "", "warning": false} ``` As one can see there is no end_line_no/end_line_pos.	2024-11-27 22:17:02 +09:00
Shad	712b4b3a97	Add support for sqlfluff 3.0.0 (#4743) ... As stated in the changelog: "the original fields of line_pos and line_no have been renamed to start_line_pos and start_line_no, to distinguish them from the new fields starting end_*"	2024-03-14 09:09:56 +09:00
w0rp	ae1d051504	#4454 Clean up more tests and code ... * Remove some tests we no longer need * Delete blocks of redundant code * Compress some tests together to simplify them * Remove a little code for ancient linter versions * Escape more executables we didn't escape before * Rename a deno option that didn't match our conventions	2023-09-16 22:23:30 +01:00
Carl Smedstad	6c4be47437	Implement support for SQL linter sqlfluff (#4361)	2022-11-21 19:50:45 +09:00