From 7b36c20036117ee85331a0e209ecae34321da284 Mon Sep 17 00:00:00 2001 From: sumeyye Date: Thu, 24 Jul 2025 14:20:08 +0300 Subject: [PATCH] fix: typos and some comments --- .../ui/angular/confirmation-service.md | 23 +++++++++++-------- .../framework/ui/angular/service-proxies.md | 2 +- docs/en/framework/ui/angular/theming.md | 1 - .../framework/ui/angular/toaster-service.md | 2 +- 4 files changed, 16 insertions(+), 12 deletions(-) diff --git a/docs/en/framework/ui/angular/confirmation-service.md b/docs/en/framework/ui/angular/confirmation-service.md index 5cafb9c700..f9b71ad21b 100644 --- a/docs/en/framework/ui/angular/confirmation-service.md +++ b/docs/en/framework/ui/angular/confirmation-service.md @@ -39,7 +39,7 @@ You can subscribe to the confirmation closing event like below: import { Confirmation, ConfirmationService } from '@abp/ng.theme.shared'; import { inject } from '@angular/core'; -// Sınıf içinde: +// inside the class: private confirmation = inject(ConfirmationService); this.confirmation @@ -135,18 +135,23 @@ this.confirmation.clear(); You can change icons with the `withConfirmationIcon()` method of `provideAbpThemeShared` function in the app.module.ts. The changes will affect all confirmation popup in the project. ```ts -import { provideAbpThemeShared, withConfirmationIcon } from '@abp/ng.theme.shared'; +import { + provideAbpThemeShared, + withConfirmationIcon, +} from "@abp/ng.theme.shared"; @NgModule({ providers: [ // ... - provideAbpThemeShared(withConfirmationIcon({ - info: 'fa fa-info-circle', - success: 'fa fa-check-circle', - warning: 'fa fa-exclamation-triangle', - error: 'fa fa-times-circle', - default: 'fa fa-question-circle', - })), + provideAbpThemeShared( + withConfirmationIcon({ + info: "fa fa-info-circle", + success: "fa fa-check-circle", + warning: "fa fa-exclamation-triangle", + error: "fa fa-times-circle", + default: "fa fa-question-circle", + }) + ), ], }) export class AppModule {} diff --git a/docs/en/framework/ui/angular/service-proxies.md b/docs/en/framework/ui/angular/service-proxies.md index 736a9ffa73..23e17b9759 100644 --- a/docs/en/framework/ui/angular/service-proxies.md +++ b/docs/en/framework/ui/angular/service-proxies.md @@ -89,7 +89,7 @@ The `generate-proxy` command generates one service per back-end controller and a A variable named `apiName` (available as of v2.4) is defined in each service. `apiName` matches the module's `RemoteServiceName`. This variable passes to the `RestService` as a parameter at each request. If there is no microservice API defined in the environment, `RestService` uses the default. See [getting a specific API endpoint from application config](./http-requests#how-to-get-a-specific-api-endpoint-from-application-config) -The `providedIn` property of the services is defined as `'root'`. Therefore there is no need to provide them in a module. You can use them directly by injecting them as shown below: +The `providedIn` property of the services is defined as `'root'`. Therefore there is no need to provide them in a module. You can use them directly by injecting as shown below: ```js import { BookService } from '@proxy/books'; diff --git a/docs/en/framework/ui/angular/theming.md b/docs/en/framework/ui/angular/theming.md index 177d87c382..401b929d14 100644 --- a/docs/en/framework/ui/angular/theming.md +++ b/docs/en/framework/ui/angular/theming.md @@ -207,7 +207,6 @@ import { inject } from '@angular/core'; const sessionState = inject(SessionStateService); sessionState.setLanguage('en'); -} ```` diff --git a/docs/en/framework/ui/angular/toaster-service.md b/docs/en/framework/ui/angular/toaster-service.md index 4c5246904f..41ca75949d 100644 --- a/docs/en/framework/ui/angular/toaster-service.md +++ b/docs/en/framework/ui/angular/toaster-service.md @@ -39,7 +39,7 @@ Options can be passed as the third parameter to `success`, `warn`, `error`, and import { Toaster, ToasterService } from '@abp/ng.theme.shared'; import { inject } from '@angular/core'; -// Sınıf içinde: +// inside the class private toaster = inject(ToasterService); //...