Consider public fields for source/target content-assist
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by locating the source/target content-assist entry points in the Eclipse plug-in and review how fields are currently handled. The issue body provides no acceptance criteria, so confirm the intended public-field behavior and add tests that demonstrate the agreed result.
Written by the indexing model from the issue text.
Description
This issue has no description.
- 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
- 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.
More from mapstruct/mapstruct-eclipse
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mapstruct/mapstruct-eclipse#50 · 4 comments ·
-
help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapstruct/mapstruct-eclipse#49 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in mapstruct/mapstruct-eclipse
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·