Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No Code completions anymore?

Open
#50 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

Research direction

No repository files, tests, or entry points are named. Reproduce the example in Eclipse 2023-09 with MapStruct Tools 0.1.0.201701192129, inspect the reported error log, and compare completion behavior with non-blocking completions enabled and disabled. Done means @Mapping code completions work for the supplied mapper example.

Written by the indexing model from the issue text.

Description

help wanted

I'm hesitant to post this as issues like this tend to be a misconfig somewhere...

I'm no longer getting any code completions at all from MapStruct. I initially thought this was because we used records almost exclusively everywhere, but now I tried to create a simple POJO and that offers no code completions for @Mapping either.

Eclipse 2023-09, MapStruct Tools 0.1.0.201701192129. The error log seems clear. Enabling or disabling "Enable non-blocking completions" makes no difference.

Example code:

@Mapper
public interface AhaMapper {
    @Mapping(target = "name", source = "name2")
    Aha fromDto2(Aha2 ahaaa);
}

public static class Aha {
    private final String name;

    public Aha(String name) {
        this.name = name;
    }

    public String getName() { return name; }
}

public static class Aha2 {
    private final String name2;

    public Aha2(String name2) {
        this.name2 = name2;
    }

    public String getName2() { return name2; }
}
Dominant language
Java
Stars
12
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from mapstruct/mapstruct-eclipse

All issues in mapstruct/mapstruct-eclipse

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.