We've used the provided documentation in order to add a new property to the IdentityRole entity:
*Project.Domain.Shared/ProjectModuleExtensionConfigurator.cs*
public static class ProjectModuleExtensionConfigurator
{
private static readonly OneTimeRunner OneTimeRunner = new OneTimeRunner();
public static void Configure()
{
OneTimeRunner.Run(() =>
{
ConfigureExistingProperties();
ConfigureExtraProperties();
});
}
private static void ConfigureExistingProperties()
{
}
private static void ConfigureExtraProperties()
{
/* https://docs.abp.io/en/abp/latest/Module-Entity-Extensions */
ObjectExtensionManager.Instance.Modules().ConfigureIdentity(identity =>
{
identity.ConfigureRole(role =>
{
role.AddOrUpdateProperty<bool>(
RoleConsts.IsGlobalPropertyName,
options =>
{
options.Attributes.Add(new RequiredAttribute());
options.Attributes.Add(new DefaultValueAttribute(false));
});
});
});
}
}
What we've found is that this adds a new column to the Roles table in the angular front end, but does not add the field to the create/edit Role modals. Digging some more, we found the documentation for Dynamic Form Extensions, and configured this for Roles:
*/src/app/core/prop-contributors.ts*
import { eIdentityComponents, IdentityCreateFormPropContributors, IdentityEditFormPropContributors } from '@volo/abp.ng.identity';
import { ePropType, FormProp, FormPropList } from '@abp/ng.components/extensible';
import { IdentityRoleDto } from '@volo/abp.ng.identity/proxy';
const isGlobalProp = new FormProp<IdentityRoleDto>({
type: ePropType.Boolean,
name: 'isGlobal',
displayName: 'Is Global',
validators: () => [],
});
export function isGlobalPropContributor(propList: FormPropList<IdentityRoleDto>) {
propList.addByIndex(isGlobalProp, 1);
}
export const roleCreateFormPropContributors: IdentityCreateFormPropContributors = {
// enum indicates the page to add contributors to
[eIdentityComponents.Roles]: [
isGlobalPropContributor,
// You can add more contributors here
]
};
export const roleEditFormPropContributors: IdentityEditFormPropContributors = {
// enum indicates the page to add contributors to
[eIdentityComponents.Roles]: [
isGlobalPropContributor,
// You can add more contributors here
]
};
*/src/app/app-routing.module.ts*
// ...
{
path: 'identity',
loadChildren: () => import('@volo/abp.ng.identity').then(m => m.IdentityModule.forLazy({
createFormPropContributors: roleCreateFormPropContributors,
editFormPropContributors: roleEditFormPropContributors
})),
},
// ...
Despite this, no new field is appearing on the Create/Edit Role modals.
We also considered/tried to replace the RoleComponent using component replacement, but this would require us to completely rewrite the role component and it's associated behaviour (CRUD, claims, permissions, move users, etc), which we do not want to do.
How can we achieve our goal of managing this new property within the Roles modal?
I'm reviewing the documentation for Localization and I'm not finding any information on how to create a custom localization provider. I thought I had seen this before, but can't find it now.
We're looking to continue using the existing out of box localization functionality, but we'd like to augment this to load resources from a custom table within our database. The intent is to be able to continue to use IStringLocalizer (L["<KEY>"]) on the server and abpLocalization pipe in angular to reference both out-of-the-box json-based resources and resources stored in our custom database table.
In our Angular application we've defined our navigation items in src/app/route.provider.ts and defined our routes within src/app/app-routing.module.ts with additional child routes loaded from lazy-loaded modules referenced within it.
We're finding that items in the navigation menu that have sub-items don't stay open/expanded (as the out of the box Administration menu does) when visiting child routes. Possibly related, we note that the breadcrumbs rarely show the correct location either.
Are we missing something obvious here? Does this just not work with lazy-loaded routes?