We are experiencing issues with proxy updates in the frontend. After updating the ABP service proxy using abp generate-proxy -t ng -u http://localhost:44354 -m [module name] --target [module name], the expected changes are not being reflected in the Angular application for some APIs. This leads to inconsistencies between the backend API and the generated service proxies, affecting functionality.
API with Array Parameters Not Generated Correctly
We encountered an issue with the proxy generation where an API in Swagger correctly accepts two arrays in its body, but the generated service proxy structure in Angular does not include these arrays in the request payload
(Swagger Receiving 2 arrays in a request body)
(Proxy request structure is missing body in its payload)
Incorrect Parameter Mapping in Generated Proxy
The generated proxy method for the API getPendingRequestsForActorFilterByBeneficiaryType... contains an incorrect parameter mapping. Specifically, in the params object, userId is mistakenly assigned the value of cancellationToken, while UserId is completely missing from the request.
Expected Correct Proxy Code:
Incorrect Parameter Mapping in Generated Proxy
the generated import paths are incorrect. The issue occurs because the import paths do not reflect the correct module folder structure, which varies based on the module name.
Generated Proxy (Incorrect Import Path):
Expected Correct Import Path:
Missing Imports in Generated Proxies
many files are missing required imports for DTOs and models. This leads to build-time errors in Angular due to undefined types.
Examples of Missing Imports:
Correct Import That Should Be Generated:
import { LookupDto } from '@proxy/shared';
1 Answer(s)
-
0
Hi,
In order to understand and reproduce your question more accurately, could you please send the ApplicationService interface, its implementation and the content of your Controller if you have created one.
