This is primarily a bugfix release. Most notably this solves some of the issues introduced in 2.0.1 around spacing within datatypes. Expressions like 1.0::double precision should now be spaced correctly.
Beyond that, this contains a selection of smaller bugfixes and dialect improvements. Even for a relatively small release we saw three new contributors (thanks @aurany, @JackWolverson & @mikaeltw 🎉).
The one new feature (as such) is being able to now configure LT05 (aka layout.long_lines) to optionally move trailing comments after the line they are found on, rather than the default behaviour of moving them up and before. Users can enable this with the trailing_comments configuration setting in the indentation section.
This release also contains some performance optimisations in the parser, especially on queries with heavily nested expressions. There will be more to come in this space, but we hope this leads to a better experience for many users. 🚀
This is mostly a bugfix release addressing some of the issues from the recent 2.0 release. Notable fixes are:
Spacing for (as applied by LT01) for datatypes, hyphenated identifiers and casting operators.
Several bugs in the indentation routines (LT02), in particular with implicit indents.
Fixing a conflict between LT09 and LT02, by only limiting LT09 to bringing targets onto a single line if there is only one select target and that it contains no newlines.
Supporting arrays, and the new rules configuration more effectively in pyproject.toml.
Configuring dialects on a file by file basis using inline comments now works.
This release also brings one small new feature in allowing additional flags to be passed to SQLFluff when called as a pre-commit hook.
Thanks especially to @JavierMonton and @LauraRichter who made their first contributions to the project as part of this release! 🎉🏆
This is primarily a bugfix release. Most notably this solves some of the
issues introduced in 2.0.1 around spacing within datatypes. Expressions
like 1.0::double precision should now be spaced correctly.
Beyond that, this contains a selection of smaller bugfixes and dialect
improvements. Even for a relatively small release we saw three new
contributors (thanks @aurany, @JackWolverson
& @mikaeltw 🎉).
The one new feature (as such) is being able to now configure LT05
(aka layout.long_lines) to optionally move trailing comments after
the line they are found on, rather than the default behaviour of moving
them up and before. Users can enable this with the trailing_comments
configuration setting in the indentation section.
This release also contains some performance optimisations in the parser,
especially on queries with heavily nested expressions. There will be more
to come in this space, but we hope this leads to a better experience for
many users. 🚀
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps sqlfluff from 1.4.5 to 2.0.2.
Release notes
Sourced from sqlfluff's releases.
... (truncated)
Changelog
Sourced from sqlfluff's changelog.
... (truncated)
Commits
e0251db
Prep version 2.0.2 (#4597)cd5d50b
Parse Caching (#4576)74539b2
Data type spacing (#4592)76f208b
MySQL: allow quoted literal in alias name (#4591)795e3b3
Make implicit indents visible in the parse tree (#4584)d9665ec
Fix #4559: TSQL implicit indents on WHERE (#4583)d1e7662
Added keywords to DB2 dialect from IBM docs (#4575)601155b
Remove matches_target_tuples (#3873) (#4561)9e8caba
Use terminators in BaseExpression (#4577)c69ff2b
Address #1630: Optionally move comments after long line (#4558)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)