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

data object docs for getter and setters are not available on the model

Open
#220 0 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

Research direction

No files, tests, or entry points are named. Start by locating the model representation and documentation collection for data-object properties; determine how getter, setter, and common documentation are currently exposed. Done means getter and setter docs are available separately while languages that do not distinguish them can still use a common doc.

Written by the indexing model from the issue text.

Description

Getters and setters are seem as properties and for each property the model just exposes 1 doc value, usually the getter, which means that for languages that distinguish Getters and setters the docs will be wrong as they are both the same.

Probably both docs should be collected and exposed individually while a common doc would still available for languages that do not need the distinction.

Dominant language
Java
Stars
111
Forks
88
PR merge metrics
No merged PRs in 30d

Getting set up

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 eclipse-vertx/vertx-codegen

All issues in eclipse-vertx/vertx-codegen

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.