Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fixes using the wrong object factory when multiple factories with the same target type but different source types are used #1313

Merged
merged 1 commit into from
Jun 3, 2024

Conversation

latonz
Copy link
Contributor

@latonz latonz commented Jun 1, 2024

Includes the source and target type when caching the resolved object factory for a given type pair instead of only the target type. This fixes a bug when using multiple object factories with the same return type but different parameter types and multiple mappings using these different object factories.

Fixes #1312

…h the same target type but different source types are used
@latonz latonz self-assigned this Jun 1, 2024
@latonz latonz enabled auto-merge (squash) June 1, 2024 03:29
@latonz latonz requested a review from CommonGuy June 1, 2024 03:29
@latonz latonz merged commit 51aa1da into riok:main Jun 3, 2024
17 checks passed
@latonz latonz deleted the 1312-object-factory-source-type branch June 3, 2024 13:56
Copy link

github-actions bot commented Jun 3, 2024

🎉 This PR is included in version 3.6.0-next.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

🎉 This PR is included in version 3.6.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

With multiple ObjectFactory methods in the same class Mapperly is choosing the wrong one.
2 participants