Sqlfluff

Latest version: v3.0.6

Safety actively analyzes 630130 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 23 of 24

0.0.9

Not secure
- Add the quick fix option to view the SQLFluff documention on the SQLFluff website.
- Fix the diagnostics so the quick fix can be triggered by any location on the problem word.

0.0.8

- This release rewrites some of the extension code, but should leave the functionality the same.
- There is now an output channel (SQLFluff) that contains additional information about the commands and can help with debugging.
- The `executablePath` and `config` settings can now make use of configuration variables.
- (https://github.com/sqlfluff/vscode-sqlfluff/pull/59) Fix issues with spawned procs, stdin use, env, and output.
- Takes inspiration from (https://github.com/sqlfluff/vscode-sqlfluff/pull/56) Fix issues with spawned procs, stdin use, env, and output.

0.0.7

Not secure
Added

- Added a `sqlfluff fix` as a command to implement auto-fixing of linting
errors. For now only `L001` is implemented as a rule that can fix things.
- Added a `rules` command to introspect the available rules.
- Updated the cli table function to use the `testwrap` library and also
deal a lot better with longer values.
- Added a `--rules` argument to most of the commands to allow rule users
to focus their search on a specific subset of rules.

Changed

- Refactor the cli tests to use the click CliRunner. Much faster

0.0.6

Not secure
Added

- Number matching

Changed

- Fixed operator parsing and linting (including allowing the exception of `(*)`)

0.0.5

Not secure
Added

- Much better documentation including the DOCS.md

Changed

- Fixed comma parsing and linting

0.0.4

Not secure
Added

- Added operator regexes
- Added a priority for matchers to resolve some ambiguity
- Added tests for operator regexes
- Added ability to initialise the memory in rules

Page 23 of 24

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.