Mapper: Option to ignore property if empty for export

Open
#64 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Locate the Mapper export entry point and inspect how empty strings, collections, and maps are currently handled. Compare the requested behavior with Jackson's @JsonInclude(NON_EMPTY); done means users can configure these empty values to be omitted during export, with the behavior verified for each mentioned value type.

Written by the indexing model from the issue text.

Description

beanmapper

For more complex beans it is interesting to allow users to define that a String/collection/map is empty that it should not be exported. Thinking of something similar to Jackson's @JsonInclude(NON_EMPTY).

Dominant language
Java
Stars
44
Forks
21
Avg merge
2d 2h
Merged PRs (30d)
3

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.

More from AuthMe/ConfigMe

All issues in AuthMe/ConfigMe

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.