mapper-customization

To customize Mapster mappings safely, define a partial Mapper class annotated with [SpiderlyDataMapper] and override the generated mapping methods. This prevents the code generator from overwriting your custom DTO projections and computed fields during regeneration.

You can add computed fields to a DTO projection by overriding the generated TypeAdapterConfig methods in a partial class. This allows you to inject custom logic for entity-to-DTO mappings while maintaining the baseline generated mappings.

The [SpiderlyDataMapper] attribute marks user-created partial Mapper classes to separate custom mapping logic from generated baseline code. It ensures the generator recognizes and preserves your overridden methods during code regeneration.

Yes, you can apply inline mappings by adjusting projections using [ProjectToDTO] attributes alongside generated TypeAdapterConfig methods. This supports tailored DTO-to-entity and entity-to-DTO behavior across multiple entities.

Yes, overriding Spiderly-generated mappers supports customization across multiple entities and projects. You can tailor mappings wherever computed fields, custom projections, or specific DTO and entity shapes are required.