MapsterMapper/Mapster

Tweaking null propagation easily

Open

#740 opened on Dec 11, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (312 forks)batch import
help wantedimprovement

Repository metrics

Stars
 (3,995 stars)
PR merge metrics
 (Avg merge 12d 15h) (10 merged PRs in 30d)

Description

Is there an easy way to change how null propagation works?

  1. If we wanted to throw an exception when null reference encountered? There are lots of various Ignore methods, similarly I wish there were Required methods or maybe an ThrowIfNull argument to be passed in
  2. If null encountered, use a provided value (I know atm it uses default or null value)

Contributor guide

Research direction
Examine the current null propagation mechanism in Mapster. Identify where null handling occurs and propose a new configuration option (e.g., ThrowOnNull or DefaultOnNull) that can be set globally or per mapping. Implement the option and add tests.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#Mapster
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60