redhat-developer / redhat-developer/vscode-java

can you support .editorconfig for linting ?

Open
#2,565 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement formatter
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

it seems to me linting/formatting only works with .xml file, but can you support maybe .editorconfig as well being the standard out there for all languages, as it seems to me this extension conflicts with vscode editorconfig extension.
e.g. my colleagues exported an xml from a java project, to .editorconfig, but now when i apply the formatting i see it all changing the files ( i would expect it to stay the same), or to be able to "detect" the .editorconfig in the root folder

https://www.freecodecamp.org/news/how-to-use-editorconfig-to-standardize-code-styles/

https://www.jetbrains.com/help/idea/editorconfig.html

https://editorconfig.org/

Cheers!

And thanks for this awesome extension 🎉 🎉 🎉 😺

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.

Research direction

Start by reviewing the existing XML-based linting and formatting behavior in the vscode-java extension, then compare it with the reported .editorconfig conflict and root-folder detection request. Done means the extension can account for .editorconfig settings without unexpectedly changing files or conflicting with the VS Code EditorConfig extension.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.