Hi,
Applying the Angular tutorial helps you to understand the structure.
We'll send the source code via email.
Angular UI supports the component replacement. It can't support specific customization because some of our components are so complex. Some attributes, ids, styles, etc. are too critical. If the user removes any of these, it may break the app.
You can replace the LoginComponent. See the description to learn implementation. We will provide documentation related to this topic.
| Component key | Description |
|----------------------------------------------------|-------------------------|
| Account.LoginComponent | Login page |
| Account.RegisterComponent | Register page |
| Account.ManageProfileComponent | Manage profile page |
| Account.ForgotPasswordComponent | Forgot password page |
| Account.ResetPasswordComponent | Reset password page |
| Account.AccountComponent | The component that wraps register, login, forgot password, and reset password pages. Contains <router-outlet>. |
| Account.ChangePasswordComponent | Change password form in manage profile page |
| Account.PersonalSettingsComponent | Personal settings form in manage profile page |
| Account.TenantBoxComponent | Tenant changing box in account component |
| AuditLogging.AuditLogsComponent | Audit logs page |
| Identity.UsersComponent | Users page |
| Identity.RolesComponent | Roles page |
| Identity.ClaimsComponent | Claim types page |
| IdentityServer.IdentityResource | Identity resources page |
| IdentityServer.Client | Clients page |
| IdentityServer.ApiResource | Api resources page |
| LanguageManagement.Languages | Languages page |
| LanguageManagement.LanguageTexts | Language texts page |
| Saas.TenantsComponent | Tenants page |
| Saas.EditionsComponent | Editions page |
| FeatureManagement.FeatureManagementComponent | Features modal |
| PermissionManagement.PermissionManagementComponent | Permissions modal |
| SettingManagement.SettingManagementComponent | Setting Management page |
Can you check the ~/.dotnet/tools folder? Is there abp file? It may be installed in a different folder.
This document can help you.
I use macOS, I have encountered the same problem. My problem was solved when I added the dotnet path. Perhaps you may have missed a solution step.
Check your Node version with this command:
node --version
It must be v10.x.x.
If Node version is correct, you can remove yarn.lock, package-lock.json, node_modules and run the npm install.
If the problem is still not resolved please run the following command to install depended ABP packages manually:
npm install @abp/ng.core @abp/ng.theme.shared @abp/ng.feature-management @abp/ng.permission-management @abp/ng.setting-management @abp/ng.setting-management.config
Did you run the yarn command to install packages? Packages may not be installed correctly, please make sure that you have the node_modules/@abp folder.
Hi,
Can you clear the local storage and session storage?
When you logged in, the token response is stored in the local storage. When you create a new solution, you should clear the browser storage.
If this suggestion will not solve the problem, please share application-configuration response with us.
Hi @bhyatz,
You have two options to create a new module in a single Angular solution. You can create a regular module or create a library.
In short, Angular libraries are modules that can be published easily.
Angular CLI can be used for both options.
See the Angular CLI documentation
You can use the following command in the Angular application root folder to create a new module.
The same way followed in the Angular-MongoDB tutorial.
yarn ng generate module <your-module-name> --route <your-module-name> --module app.module
If you use the above command, it will create a lazy-loaded module in the app/<your-module-name> folder.
You can use the following command to create a library
yarn ng generate library <your-library-name>
If you execute the above command, it will create a library in the projects/<your-library-name folder. This library can be used in your Angular application. You can import any module, component, directive, etc., from this library.
See the Angular libraries guide
Note: If you don't plan to publish any library to an NPM server, making each module a library will complicate your angular application.
If you generate a module with ABP CLI, an Angular application with two libraries will be created. You must publish these Angular libraries to use in your main solution.
If you chose this way, Symlink Manager may help you. Symlink Manager is a JS package that easily manages to symbolic link processes of your dependency packages.