Hello,
Can you send me response of api/abp/api-definition?includeTypes=true
endpoint. Sorry for the request again. I forgot to ask with the includeTypes parameter in the first asking.
I think I found the solution. I will try to fix it in the next version of 5.3.
But there is a workaround for the error. If you increase the stack size of NodeJs, the command works properly. Add the command below to your package.json;
//package.json
{
"scripts": {
"generate-proxy": "node --stack-size=1200 ./node_modules/.bin/ng g @abp/ng.schematics/collection.json:proxy-add --module __default --apiName __default --source __default --target __default --url https://YOUR_URL"
}
And run the command with
yarn generate-proxy
or
npm run generate-proxy
Hello,
Can you share your ABP Suite logs?
Suite logs placed under
Windows: %UserProfile%\.abp\suite\logs
Mac: ~/.abp/suite/logs
Hello,
Currently, we do not support this feature. But we have plans to develop the "preserve custom code" feature for the Abp Suite in the next milestones
Hello,
I created a new app with ABP version 5.3.3. I tried proxy generation with url param. Proxy generation works fine as expected.
I took a screen recording. You can access the related video from this link
Can you share the result of 'yarn why @abp/ng.schematics' command in your angular directory?
Hello,
The range error does not seem related to the microservice template. You can look at the another support question.
I was able to reproduce the range error. You can follow the status of issue
Hello,
Did you update the "@abp/ng.schematics" package version also?
I was able to reproduce the range error. You can follow the status of issue
Hello,
Sorry for the late response.
We fixed the error related to url parameter in version 5.3.0-rc.2
Could you send the response of api/abp/api-definition
endpoint so we can understand the issue you are facing?
Hello,
Sorry for the late response.
The problem is there are no libs for each microservices in the microservice angular project. We will modify our microservice angular template and configure proxy generation and ABP Suite for this case.
We have found a temporary solution for using suite and abp proxy generation. Please follow the steps below;
abp new YourNameSpace.YourServiceName -t module-pro --csf
"your-service/config": ["projects/your-service/config/src/public-api.ts"]
//app.routing.module.ts
{
path: 'your-service',
loadChildren: () => import('your-service').then(m => m.YourServiceModule.forLazy()),
}
route.provider.ts
//app.module.ts
import { NgModule } from '@angular/core';
import { YourServiceConfigModule } from 'your-service/config';
@NgModule({
declarations: [AppComponent],
imports: [
//other imports
YourServiceConfigModule.forRoot(),
]
})
export class AppModule {}
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.
Hello,
Currently, proxy generation in angular microservice templates needs extra steps. We will work on this. Please follow steps in gist