Hi again, This messages is warning which means problem fixed, the reason of that there are peer dependencies on libraries. It must run correct right now ?
Hello,
I've tried to reproduce error but I didn't
angular
foldernpm install
Hello,
Can you add codes below to angular.json > styles section
{
"input": "node_modules/@volosoft/ngx-lepton-x/assets/css/font-bundle.css",
"inject": false,
"bundleName": "font-bundle"
},
{
"input": "node_modules/@volosoft/ngx-lepton-x/assets/css/font-bundle.rtl.css",
"inject": false,
"bundleName": "font-bundle.rtl"
}
Hello, I've created an issue for that also I refunded your credit. This issue will fixed at 7.2-patch 🙂
Hello Alexander,
For the customize guard system you can customize PermissionGuard like below
//custom-permission.guard.ts
import { HttpErrorResponse } from '@angular/common/http';
import { Injectable } from '@angular/core';
import { ActivatedRouteSnapshot, RouterStateSnapshot } from '@angular/router';
import { Observable, of, switchMap, tap } from 'rxjs';
import { PermissionGuard } from '@abp/ng.core';
@Injectable({
providedIn: 'root',
})
export class CustomPermissionGuard extends PermissionGuard {
canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): Observable<boolean> {
let { moduleId } = route.data || {};
return super.canActivate(route, state).pipe(
switchMap(access => {
if (!access) {
return of(false);
}
if (!moduleId) {
return of(true);
}
//Custom logic
return of(true);
}),
tap(access => {
if (!access && this.oAuthService.hasValidAccessToken()) {
this.httpErrorReporter.reportError({ status: 403 } as HttpErrorResponse);
}
}),
);
}
}
//app.module.ts
import { PermissionGuard } from '@abp/ng.core';
import { CustomPermissionGuard } from './custom-permission.guard';
@NgModule({
imports: [],
providers: [
{
provide: PermissionGuard,
useExisting: CustomPermissionGuard,
},
],
declarations: [AppComponent],
bootstrap: [AppComponent],
})
export class AppModule {}
//app-routing.module.ts
const routes: Routes = [
{
path: 'identity',
loadChildren: () => import('@abp/ng.identity').then(m => m.IdentityModule.forLazy()),
data: {
moduleId: 'Identity',
},
},
];
@NgModule({
imports: [RouterModule.forRoot(routes, {})],
exports: [RouterModule],
})
export class AppRoutingModule {}
Hello,
The bug fixed, you can update to 7.2.3 or 7.3.0
after publish. I'm closing this question :)
Hello fj
I'm working on it, we taking this error on authorization code flow, I've created an internal issue for that. I'll fix that
Hello again, You don't need to test it. We find the original issue here's the link: https://github.com/abpframework/abp/issues/16818 you can follow this issue. After the close issue I'll update commercial side's component for users. I'm closing this Question. If problem won't fix I'll re-open
Hello mk@incyan.com,
I've re-produce your issue I've create an issue for that, I also refunded your credit. It'll fix with 7.2-patch and 7.3-final
Hi again Mustafa,
Have you tried to create and test steps with CLI, does the error persist ?