Describe accessor naming strategies

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

The issue body names no files, tests, or entry points. Start by locating the site's existing documentation about accessor naming strategies and determine where this topic belongs; done should mean the strategy behavior is clearly described in the appropriate documentation.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
CSS
Stars
71
Forks
40
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.org

All issues in mapstruct/mapstruct.org

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.