microsoft / microsoft/vscode-pgsql
Is linting available?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 395
- Forks
- 33
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 3
Description
Is there meant to be linting available to check for basic syntax errors like missing/extra commas? I tried typing some incorrect code but don't see any linting messages. I have PG-SQL IntelliSense available and I'm getting suggestions for table names and columns.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the PG-SQL IntelliSense extension behavior described in the issue and whether it currently reports syntax diagnostics for incorrect SQL. Determine whether basic missing or extra comma errors are expected to produce linting messages; done means the availability and intended behavior are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, vscode
- Domain
- databases, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100