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

ABP 9 Modular Angular Project: Is the Proxy Generation Command Run for the Module? #22124

Open
ayshamougamadou opened this issue Feb 11, 2025 · 0 comments

Comments

@ayshamougamadou
Copy link

I have created an ABP Modular application using the Angular framework, and I've noticed that the proxy folder exists in the main application. Upon inspecting the generated proxies, it seems that services from my module are included within the main application's proxy folder.

I was under the impression that proxies for each module would be generated separately. Can you clarify if the proxy generation process consolidates all module services into the main application’s proxy folder, or is there a configuration step needed to separate the proxies for each module?"

this is my tsconfig.json in my module app.

{
"extends": "./tsconfig.prod.json",
"compilerOptions": {
"paths": {
"@ordering": [
"projects/ordering/src/public-api.ts"
],
"@ordering/config": [
"projects/ordering/config/src/public-api.ts"
],
"@Proxy": ["projects/ordering/src/lib/proxy/index.ts"],
"@proxy/": ["projects/ordering/src/lib/proxy/"]
}
}
}

I noticed that there is a @Proxy alias set up in the tsconfig.json, but I can't find the generated proxy folder in the module itself. Can you confirm if the abp generate-proxy command needs to run specifically for the module, or does it need to be run from the host application instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants