redhat-developer / redhat-developer/vscode-java
Editor encoding inherited from Maven
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
If we have a Maven project and its POM tag "project.build.sourceEncoding" is different from the editor's default "files.encoding", it would be helpful if VS Code could notify us of this or automatically set the Maven encoding in the "files.encoding" setting of workspace's settings.json file.
Currently I have to check it and change it manually.
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
Start by locating the extension's Maven project handling and the integration point for VS Code's files.encoding workspace setting. Compare project.build.sourceEncoding with the editor default in a Maven project, then clarify whether completion means a notification, an automatic workspace update, or both, with behavior verified for matching and differing encodings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100