eclipse-lsp4e / eclipse-lsp4e/lsp4e

Configure 'Organize Imports' to avoid unecessary commit noise.

Open
#1,423 1 comment 1 reaction 1 assignee View on GitHub

@sebthom is already working on this.

Since Nov 26, 2025.

Dominant language
Java
Stars
85
Forks
69
Avg merge
8h 33m
Merged PRs (30d)
6

Description

I noticed that some of my recent PR's changed wildcard imports to actual imports, e.g.,

import static org.junit.jupiter.api.Assertions.*;
// vs
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertTrue;

I think this comes from the fact, that the LSP4E projects don't have project specific settings for handling imports, e.g.:
Image

Thus, the IDE falls back to the workspace settings, which are probably different for every committer.
To avoid unnecessary commit noise we should probably configure these settings.

Personally, I'm leaning slightly toward named imports, but in the end, I don't really care, as long as we all use the same settings.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.