are u talking about this?
logical-model-route-provider.ts
import { RoutesService, eLayoutType } from '@abp/ng.core';
import { APP_INITIALIZER } from '@angular/core';
export const LOGICAL_MODELS_ROUTE_PROVIDER = [
{ provide: APP_INITIALIZER, useFactory: configureRoutes, deps: [RoutesService], multi: true },
];
function configureRoutes(routes: RoutesService): any {
return () => {
routes.add([
{
path: '/logical-models',
name: '::Menu:LogicalModels',
layout: eLayoutType.application,
requiredPolicy: 'Models.Logical',
parentName: '::Menu:Models',
},
]);
};
}
app.component.ts
constructor(
private idleService: IdleService,
private settingTabs: SettingTabsService,
private userMenuService: UserMenuService,
private config: ConfigStateService,
private navItems: NavItemsService,
private ngSelectConfig: NgSelectConfig,
private replaceableComponents: ReplaceableComponentsService,
private routes: RoutesService,
private modal: NgbModal,
private oAuthService: OAuthService,
private stickyFilterService: StickyFilterService,
private dynamicIdService: DynamicIdService,
) {
this.replaceableComponents.add({
component: FooterComponent,
key: eThemeLeptonXComponents.Footer,
});
this.replaceableComponents.add({
component: BreadcrumbComponent,
key: eThemeLeptonXComponents.Breadcrumb,
});
this.routes.patch('::Menu:LogicalModels', {
path: '/logical-models/:lModelId/logical-tables',
});
this.ngSelectConfig.appendTo = 'body';
}
logical-models-routing.module.ts
const routes: Routes = [
{
path: '',
component: LogicalModelsComponent,
canActivate: [authGuard, permissionGuard],
children: [
{
path: ':lModelId/logical-tables',
component: LogicalTablesComponent,
canActivate: [authGuard, permissionGuard],
},
],
},
logical-models.component.ts
navTables(record: LogicalModelDto): void {
this.router.navigate(['logical-models', record.id, 'logical-tables']);
}
Having some issues w/ your solution, it is not working for me.
tried patch and i tried add. i did not see anything in the left nav when i did the patch. when i did the add i saw the new left nav item. also tried when using the angular child route and not child route
both patch and add, the left nav does not remain selected
in your solution will there be a item in the left nav?
I have a left nav that shows the pages, looks screen shot 1. Then on the 'Data Transformation page there is an row action to show detail (screen shot 2) and i select that action. The left nav is no longer showing a selected menu item, even though the detail page is part of the route (yes the show detail page is not in the left nav).
Can I programmatically make the the left nav show like in screen shot 1? Data Transformation and Steps shown as selected? I tried using abp NavbarService and just expanding it by the below code. (Yes it only does part of what I want, but it doesn't work). Maybe i need to mark something dirty, call an update/refresh? Maybe this service is not designed to do this?
const item = this.navItems.find(item => item.text === 'Data Transformation');
item.expanded = true;
item.selected = true;
}
i am closing the ticket as we have figured out an alternate way to get the data. I do thank you for the effort!!!
berkansasmaz,
i did find an email for you looking through the support tickets: berkan.sasmaz@volosoft.com. i will send the email there.
In a domain module and need to get user data and users for a role (data like phone number, email, name). I have tried to use IdentityUserManager/IdentityRoleMnager and IdentityUserRepository/IIdentityRoleRepository
i added a package ref to the project <PackageReference Include="Volo.Abp.Identity.Domain" Version="8.3.4" />
I tried adding various DependsOn to the Module. Building works ok, but i get a runtime of cannot resolve, one of the messages is shown below:
Which should we be using the Managers or the Repository? What is the DependsOn we should be using? I have googled and i have seen answers for using managers and repositories. None of them have worked for me
I needed to modify the code a little, still testing.
I had issues with using renderer in a service. I found a work around.
Also had issues with some items under administration, think i found a work around for this also.
i will need to do more testing but the code was a great base to start with !!!
We are looking for a recommendation to how we can attach an id to each page. For pages we own we can add an id on to the abp-page like the id='main-content' shown below. Pages which are NOT under our control, we do not have a solution. The id will be the same for all pages, it is NOT dynamic. If you're wondering why we need this it is for 508 (accessibility)
We are looking for a recommendation.
our testing looking good, closing this ticket.
