Support for automatically fixing errors.

Open
#204 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
postgresql, rust
Domain
databases, tooling

Research direction

Start by reviewing the reported SQL capitalization and trailing-newline diagnostics in the linter. Determine which errors could be safely auto-fixed and what command or output behavior should trigger fixes; done means the proposed fixes are specified and covered by tests, but the issue names no files or tests to begin with.

Written by the indexing model from the issue text.

Description

enhancement

I don't wanna fix those errors myself becouse usually this kind of error could be fixed automatically.

16:	ALTER TABLE some_table_name drop constraint if exists constrain_name; <-- uses lowercase SQL keyword: 'constraint', use 'CONSTRAINT' please
16:	ALTER TABL some_table_name drop constraint if exists constrain_name; <-- uses lowercase SQL keyword: 'if exists', use 'IF EXISTS' please
ERROR: File should ends with ONLY ONE newline!!!
Dominant language
Rust
Stars
1.2k
Forks
70
Avg merge
52m
Merged PRs (30d)
47

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sbdchd/squawk

All issues in sbdchd/squawk

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.