MapsterMapper / MapsterMapper/Mapster
Please support arbitrary parameters on interface when generating mapper
Open
Nobody has claimed this yet.
feature request
- Dominant language
- C#
- Stars
- 5.2k
- Forks
- 410
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 6
Description
````c#
[Mapper]
public interface IMyMapper{
B Map(A a, string arbitraryString, int anotherParam );
}
class A{
string Name;
}
class B{
string Name; // maps directly from A.Name
string Val; //will be mapped from arbitraryString
int Age //will be mapped fromanotherParam ;
}
````
Contributor guide
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.
Research direction
Start by tracing the mapper code-generation path for interface methods and how method parameters are currently handled. Compare the requested A-to-B property mapping with the arbitrary string and integer parameters in the example. Done means generated mapping supports those parameters while preserving direct mappings from A.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100