@lsw-abpvue/account-core

@lsw-abpvue/account-core

The account logic that has no UI of its own, for Lsw.Abp.VueUI, an unofficial Vue UI for the ABP Framework.

It exists because two packages need the same answers and neither may depend on the other: @lsw-abpvue/account draws the login and profile pages, and @lsw-abpvue/theme-basic draws the shell they sit in, tenant box included.

pnpm add @lsw-abpvue/account-core

What is in it

const wrapper = inject(AuthWrapperService);

if (!wrapper.isLocalLoginEnabled.value) {
  // The client authenticates somewhere else; a password form would collect nothing useful.
}

Adding a tab to the profile page

A module with something to say about the signed-in user adds a tab instead of replacing the page:

inject(ManageProfileTabsService).add([
  {
    name: 'MyModule.SecurityLog',
    text: 'MyModule::SecurityLog',
    component: SecurityLogTab,
    order: 3,
    requiredPolicy: 'MyModule.SecurityLog',
  },
]);

The tree filters by permission and by the tab's own visible(), so a tab appears the moment a login grants its policy. ManageProfileStateService holds the profile the page loaded, so a tab reads and writes the same one the other tabs do.

Switching tenant

const found = await inject(TenantBoxService).switchTo('acme');

false means no tenant goes by that name, and the session is left as it was. Saying so is the caller's business: the service raises no toast, because a toast is a theme.

@lsw-abpvue/account-core/proxy

The generated proxy of ABP's Volo.Abp.Account module — AccountService, ProfileService, and the DTOs they carry. Written by abpvue proxy add --module account and checked in; a change in it in a pull request is a change in the backend's API.

Compared with the Angular UI

@abp/ng.account.core has the first two services and nothing else. The differences:

Registered in the design documents' api-parity-map.md.

Licence

MIT.