mmaldonado@emscltd.com的活动

hi, we send you an email containing the related files

Could you re-send me again that mail please, I do not see it on my inbox

hi, we send you an email containing the related files

thank you very much, by the way, could you help me keep me posted when this functionality works for microservice template please, I am updating the service definition all the time

Hello,

Currently, proxy generation in angular microservice templates needs extra steps. We will work on this. Please follow steps in gist

Note: Url parameter for angular proxy generation started to be supported in abp cli 5.2.2 and @abp/ng.schematics package version 5.2.2.

not working

I also try with ProductService, and is not working

abp generate-proxy -t ng -m ProductService -u https://localhost:44361 --target product-service [07:27:41 INF] ABP CLI (https://abp.io) [07:27:42 INF] Version 5.3.2 (Stable) npm WARN config global --global, --local are deprecated. Use --location=global instead. [Invalid Module] Backend module "ProductService" does not exist in API definition.

RangeError: Maximum call stack size exceeded at getConstructorName (node:internal/util/inspect:575:9) at formatRaw (node:internal/util/inspect:827:23) at formatValue (node:internal/util/inspect:817:10) at inspect (node:internal/util/inspect:347:10) at formatWithOptionsInternal (node:internal/util/inspect:2167:40) at format (node:internal/util/inspect:2021:10) at console.warn (D:\Repositories\NebulOS\Elevos.Phoenix\apps\angular-pcr\node_modules@angular\cli\lib\cli\index.js:45:39) at Observable._trySubscribe (D:\Repositories\NebulOS\Elevos.Phoenix\apps\angular-pcr\node_modules@abp\ng.schematics\node_modules\rxjs\internal\Observable.js:55:25) at Observable.subscribe (D:\Repositories\NebulOS\Elevos.Phoenix\apps\angular-pcr\node_modules@abp\ng.schematics\node_modules\rxjs\internal\Observable.js:30:22) at MergeMapOperator.call (D:\Repositories\NebulOS\Elevos.Phoenix\apps\angular-pcr\node_modules@abp\ng.schematics\node_modules\rxjs\internal\operators\mergeMap.js:37:23)

I think is a mistake on the steps

abp generate-proxy -t ng -m myService -u https://service-url --target my-service

should be MyService based on the example documentation in environment.ts

https://1drv.ms/u/s!An5XT7_73uQajg0cKemVDZ7mYpwF?e=78iQ76

the link should contain: swagger.json api-definition.json

I am using latest NodeJs version I also tried dotnet tool uninstall -g volo.abp.cli dotnet tool install -g volo.abp.cli --version 5.1.1 and run again the abp generate-proxy -t ng -url https://localhost:45048 abp generate-proxy -t ng -url https://localhost:44325 abp generate-proxy -t ng -url https://localhost:44361

45048 is the port for my new service 44325 is the gateway 44361 is productservice

no one is working, all of them ends on [Invalid Module] Backend module "app" does not exist in API definition.

My new service has custom endpoints

• ABP Framework version: 5.3.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): microservices template
• Exception message and stack trace:
• [Invalid Module] Backend module "productService" does not exist in API definition.
• abp generate-proxy -t ng -url https://localhost:44361
• [16:41:39 INF] ABP CLI (https://abp.io)
• [16:41:39 INF] Version 5.3.2 (Stable)
• [Invalid Module] Backend module "app" does not exist in API definition.
• Steps to reproduce the issue:"run abp generate-proxy -t ng -url https://localhost:44361 after create the microservice solution"

I think you should provide a way to create new clients, like angular and react native for microservice template, maybe throw the abp cli as new requirement