Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Exception occured when map single object from EF Core entity class (with proxy)

未关闭
#1,024 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
58/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp
领域
backend

调研方向

Start by tracing how Mapster resolves the runtime source type in Adapt<CreateApiRequest>(), comparing it with the explicit-source-type overload that succeeds. Reproduce the failure with an EF Core lazy-loading proxy and check the existing mapping tests for proxy or derived types. Done when mapping the proxy without an explicit source type succeeds while the destination-member validation remains correct.

由索引模型根据 Issue 内容生成。

描述

Hi, i'm using Mapster ver. 10.0.11, i got exception when doing single object mapping
The following members of destination class CreateApiRequest do not have a corresponding source member mapped or ignored: ...
which i have include described field in mapster config and passed TypeAdapterConfig.GlobalSettings.Compile();.

My code when call adapt:
var entity = getEntityById(id); //EF Core entity
var mapped = entity.Adapt<CreateApiRequest>(); //map with mapster, got exception here, compile is ok

As i investigated, it turns out that entity type is Proxy rather than actual type (i'm using EF LazyLoadingProxies).
Current workaround that i'm using is to specify source type when mapping:
var mapped = entity.Adapt<EntityType, CreateApiRequest>(); //this line successfully run

主要语言
C#
星标
5.2k
派生
409
平均合并
3 天 4 小时
30 天内合并 PR
3

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

MapsterMapper/Mapster 的其他 Issue

查看 MapsterMapper/Mapster 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。