mark-gerarts / mark-gerarts/automapper-plus
QUESTION : Asserting complete mapping
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 562
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
A feature of the dotnet AutoMapper is `AssertConfigurationIsValid()` which will barf if a new property was added that was not able to be automagically mapped.
I'm trying to find a way to assert the same here. A unit test that will fail if there is a destination or source property that doesn't have an operation.
How might I go about this? Am I missing something obvious already?
Contributor guide
No contributing guide indexed for this repository
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 reviewing the existing mapping configuration and the dotnet AutoMapper AssertConfigurationIsValid() behavior referenced in the issue. Determine how source and destination properties are represented, then define a failing assertion for unmapped properties and add coverage showing that complete mappings pass and missing operations fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100