- ABP Framework version: v7.4.0
- UI Type: Blazor WASM
- Database System: EF Core (SQL Server)
-
- Tiered (for MVC) or Auth Server Separated (for Angular): microservices
- Exception message and full stack trace:
- Steps to reproduce the issue:
Hi,
I would like to mention about the following error that appears after abp generate-proxy. I noticed that this error appears when we regenerate client proxies and in the api there is a reference to LookupDto. This behavior appeared in version v.7.3.2
Cheers, Iulian
5 Answer(s)
-
1
Hi,
Can you please provide the full steps to reproduce? I will check it. thanks
-
0
Hi,
It's very simple. You can take any project you have or generate the entity with abp suite. It is important that the entity has a one-to-many relationship with another entity so that LookupDto appears in Api. Then generated as usual static proxy clients. For the entities that have Lookups, errors will appear, in the order of those in the image presented later.
-
0
ok, I will check it.
-
0
Hi,
We will fix it in the next patch version. your ticket was refunded.
-
0
https://github.com/abpframework/abp/issues/17968
