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

Default mapper configuration per assembly #201

Closed
latonz opened this issue Dec 12, 2022 · 4 comments · Fixed by #657
Closed

Default mapper configuration per assembly #201

latonz opened this issue Dec 12, 2022 · 4 comments · Fixed by #657
Labels
enhancement New feature or request

Comments

@latonz
Copy link
Contributor

latonz commented Dec 12, 2022

Allow to set an attribute on the assembly level to set default configurations applied to all mappers.
These should be overwritable by configurations via a MapperAttribute on a mapper class. A mapper class still needs the MapperAttribute to mark the class to be taken into account by Mapperly.

The attribute for the assembly level configurations may use another name, since probably (now or in the future) not all and/or different options may be configurable on an assembly level.

@latonz latonz added the enhancement New feature or request label Dec 12, 2022
@latonz
Copy link
Contributor Author

latonz commented Dec 12, 2022

Rel. #199 1

@Chimaine
Copy link

I would like to support the general idea of global or sharable configurations es well. For our scenario, we would like to ignore properties on a base class, so we don't need to repeat something like [MapperIgnoreSource("Id")] on every Mapper.

@github-actions
Copy link

github-actions bot commented Sep 5, 2023

🎉 This issue has been resolved in version 3.2.0-next.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This issue has been resolved in version 3.2.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
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants