sql-formatter-org / sql-formatter-org/sql-formatter
Expose logs to VSCode frontend or describe in documentation how to reach the logs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 456
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 3
Description
The vscode plugin is not working for me in Sagemaker, it does work on my laptop. I could have sworn I DONT need to install the sql-formatter binary via npm or yarn if I install the plugin (the docs could be clearer on this--many enter the sql-formatter world via the vscode plugin). So I want to see what might be going wrong when the format command is run against my code (in vscode) but unlike most other plugins there is not output exposed to vscode (via 'output->dropdown') .
This will help tons of people find out immediately what's going wrong rather than just a lack of responsiveness from a plugin.
Contributor guide
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
The issue points to the VSCode plugin's format command and VSCode Output dropdown as the starting points; reproduce the Sagemaker failure and compare it with the laptop setup. Check the existing plugin documentation for sql-formatter installation requirements. Done means either diagnostic logs are visible in VSCode's Output dropdown or the required setup and log path are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100