Activities of "muhammedaltug"

Hello

You need to replace TenantsComponent and TenantService.

You can replace TenantComponent with the following code

import {Component} from '@angular/core';
import {ReplaceableComponentsService} from "@abp/ng.core";
import {eSaasComponents} from "@volo/abp.ng.saas";

@Component({
/* Component Metadata */
})
export class AppComponent {
  constructor(private replaceableComponentsService: ReplaceableComponentsService) {
    replaceableComponentsService.add({
      key: eSaasComponents.Tenants,
      component: YOUR_COMPONENT
    });
  }
}

And you can replace TenantService with the following code

//app.module.ts

import {NgModule} from '@angular/core';
import {MyTenantService} from "./my-tenant.service";
import {TenantService} from "@volo/abp.ng.saas";

@NgModule({
  declarations: [
  //declarations
  ],
  imports: [
    // imports
  ],
  providers: [
    // other providers
    {
      provide: TenantService,
      useClass: MyTenantService
    }
  ]
})
export class AppModule {}

Also, you can replace only the ConnectionStringsComponent in version 4.4 and abp supports multiple connection strings in version 4.4

If you upgrade your version to 4.4 you can replace ConnectionStringsComponent with the following code

import {Component} from '@angular/core';
import {ReplaceableComponentsService} from "@abp/ng.core";
import {eSaasComponents} from "@volo/abp.ng.saas";

@Component({
/* Component Metadata */
})
export class AppComponent {
  constructor(private replaceableComponentsService: ReplaceableComponentsService) {
    replaceableComponentsService.add({
      key: eSaasComponents.ConnectionStrings,
      component: YOUR_COMPONENT
    });
  }
}

Hello,

What is your "@abp/ng.schematics" version? It seems it can't resolve the URL parameter. Can you upgrade the package version to 5.2.2? We will send an example project to your email address.

Hello, You can create angular libs in the angular project for each microservice and generate proxies in related lib. In this way, proxy generation doesn't try to generate services, models, etc which were generated before. By the way, we have plans for the generating proxies to related libs as its default behavior

You can follow the steps below to avoid this problem right now:

Create an angular package with ng g library cetolresult-service

Update tsconfig paths for cetolresult-service with the following in tsconfig.json

"paths": {
    // other paths
    "cetolresult-service": ["projects/cetolresult-service/src/public-api.ts"]
  }

Update your environment file for cetolresult-service with the following in environment.ts

apis: {
    // other apis 
    CetolresultService: {
      url: 'https://localhost:45011'
      rootNamespace: 'ROOT_NAMESPACE',
    },
  }

Run the generate proxy command in the angular folder. abp generate-proxy -t ng -m cetolresultService -u https://service-url --target cetolresult-service

Update public-api.ts in packages/cetolresult-service/src/public-api.ts with following code

// other exports
export * from './lib/proxy';

Hello,

You can use OAuthService's hasValidAccessToken method for checking user has successfully logged in.

You can use angular's APP_INITIALIZER token for running control during app initialization

Hello,

Can you send your component.ts and component.html file?

Also you can check how to use ListService in documentation

Hello,

Thanks for reporting. We created an internal issue. I will inform you when the fix is available. Your credit refunded

Hello,

The warning message is wrong we fixed and it will be available in the next versions thanks for reporting

Hello,

Can you share your package.json and angular.json files?

Hello,

Can you share your app.module.ts and app-routing.module.ts ?

Did you give permission for FileManagement to the user or role?

Hello,

I responded to this issue in github just now. Can you follow the status of the issue on Github?. Your credit refunded