Thank you for providing more information. Since I could not produce your problem, could you send a sample project to this e-mail sumeyye.kurtulus@volosoft.com?
I have tried the same in my macbook. And it works over there. What can be wrong for my windows pc? Do you have any idea? I am sure that firewall is not blocking.
Hello, this should not depend on the operating system itself. Can you confirm that you have used exact the same url parameter for both trials? Because, schematics cannot reach the api and it may be running on http://localhost:44389 rather than https://localhost:44389
So, as @enisn says, you should check the version compatibilities of your package manager along with the node.js version.
Thank you for sharing details.
However, I cannot produce the problem yet. Could you tell me which package manager you are using?
Also, can you try updating @volosoft/abp.ng.theme.lepton-x package to 4.0.6 and confirm whether the problem persists?
ABP test project also uses the same way for authorization if you did not specify the password flow. So, this should not cause a problem. You can also check the published solution within the latest pre-release on this PR https://github.com/abpframework/abp/pull/22066.
Hello,
Thank you for reporting this issue. We’re aware of this and are working on a fix for an upcoming release. I am also refunding your ticket.
For now, a temporary workaround is to manually correct the affected imports and references. We appreciate your patience and will keep you updated with the releases.
Hello, I cannot produce the same problem on my end. Could you provide the update details in your package.json?
Hello, you will need to use parentName to group the navigation items.
You can follow this documentation for managing navigation elements in angular: https://abp.io/docs/latest/framework/ui/angular/modifying-the-menu#how-to-add-a-navigation-element
You can also get a reference from here for blazor: https://abp.io/docs/latest/framework/ui/blazor/navigation-menu#menu-item-properties
Hello, this problem was fixed with this release https://github.com/abpframework/abp/releases/tag/9.0.5 in this PR https://github.com/abpframework/abp/pull/22120
Hello, this problem has been fixed with the version 9.0.6
You can move @angular-eslint/builder and @angular-eslint/schematics dependencies to peerDependencies in your package.json file for the time being like this:
{
...
"private": true,
"dependencies": {
"@abp/ng.account": "~9.0.5",
"@abp/ng.components": "~9.0.5",
"@abp/ng.core": "~9.0.5",
"@abp/ng.identity": "~9.0.5",
"@abp/ng.oauth": "~9.0.5",
"@abp/ng.setting-management": "~9.0.5",
"@abp/ng.tenant-management": "~9.0.5",
"@abp/ng.theme.lepton-x": "~4.0.6",
"@abp/ng.theme.shared": "~9.0.5",
"@angular/animations": "~18.1.0",
"@angular/common": "~18.1.0",
"@angular/compiler": "~18.1.0",
"@angular/core": "~18.1.0",
"@angular/forms": "~18.1.0",
"@angular/localize": "~18.1.0",
"@angular/platform-browser": "~18.1.0",
"@angular/platform-browser-dynamic": "~18.1.0",
"@angular/router": "~18.1.0",
"bootstrap-icons": "~1.8.0",
"rxjs": "~7.8.0",
"tslib": "^2.0.0",
"zone.js": "~0.14.0"
},
"devDependencies": {
"@abp/ng.schematics": "~9.0.5",
"@angular-devkit/build-angular": "~18.1.0",
"@angular-eslint/eslint-plugin": "~18.1.0",
"@angular-eslint/eslint-plugin-template": "~18.1.0",
"@angular-eslint/template-parser": "~18.1.0",
"@angular/cli": "~18.1.0",
"@angular/compiler-cli": "~18.1.0",
"@angular/language-service": "~18.1.0",
"@types/jasmine": "~3.6.0",
"@types/node": "^12.11.1",
"@typescript-eslint/eslint-plugin": "7.16.0",
"@typescript-eslint/parser": "7.16.0",
"eslint": "^8.0.0",
"jasmine-core": "~4.0.0",
"karma": "~6.3.0",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage": "~2.1.0",
"karma-jasmine": "~4.0.0",
"karma-jasmine-html-reporter": "^1.7.0",
"typescript": "~5.5.0"
},
"peerDependencies": {
"@angular-eslint/builder": "~18.1.0",
"@angular-eslint/schematics": "~18.1.0"
}
}
