Activities of "portx-dev"

@maliming Open 2 tabs

TabA => account/login TabB => account/login

If you sign in TabA, TabA will redirect to home page At that time, TabB is still in account/login, if you sign, you will see error 400

I updated my project from 8.2.3 to 8.3.2, when creating a new entity from suite, angular ui is not generated. This is the log of the suite

2024-11-05 02:24:20.673 +07:00 [INF] 10/11 - AngularUiGenerateWithSchematicsCommand started...
2024-11-05 02:24:20.674 +07:00 [INF] Running the Angular Schematics command:
node run-schematics.mjs "D:/PortX/portx_abp/angular/.suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-pro PortX "D:/PortX/portx_abp/aspnet-core/.suite/entities/OwnerSupplierUser.json" "D:/PortX/portx_abp/angular" 
2024-11-05 02:24:25.251 +07:00 [INF] Angular Schematics command failed.
D:\PortX\portx_abp\angular\.suite\schematics\node_modules\execa\lib\error.js:60
		error = new Error(message);
		        ^

Error: Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-pro --target PortX --source D:/PortX/portx_abp/aspnet-core/.suite/entities/OwnerSupplierUser.json
',' expected. (23:30)
  21 |   
  22 |
> 23 |   createWithOcr = (input: any<string, StringValues>, config?: Partial<Rest.Config>) =>
     |                              ^
  24 |     this.restService.request<any, BillFileProcessDto>({
  25 |       method: 'POST',
  26 |       url: '/api/app/bill-file-processes/create-with-ocr',
    at makeError (D:\PortX\portx_abp\angular\.suite\schematics\node_modules\execa\lib\error.js:60:11)
    at handlePromise (D:\PortX\portx_abp\angular\.suite\schematics\node_modules\execa\index.js:118:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async file:///D:/PortX/portx_abp/angular/.suite/schematics/run-schematics.mjs:6:20 {
  shortMessage: 'Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-pro --target PortX --source D:/PortX/portx_abp/aspnet-core/.suite/entities/OwnerSupplierUser.json',
  command: '.suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-pro --target PortX --source D:/PortX/portx_abp/aspnet-core/.suite/entities/OwnerSupplierUser.json',
  escapedCommand: '".suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" --template app-pro --target PortX --source "D:/PortX/portx_abp/aspnet-core/.suite/entities/OwnerSupplierUser.json"',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: "\x1B[1m\x1B[31m',' expected. (23:30)\n" +
    '\x1B[0m \x1B[90m 21 |\x1B[31m   \n' +
    ' \x1B[90m 22 |\x1B[31m\n' +
    '\x1B[31m\x1B[1m>\x1B[22m\x1B[1m\x1B[31m\x1B[90m 23 |\x1B[31m   createWithOcr \x1B[33m=\x1B[31m (input\x1B[33m:\x1B[31m any\x1B[33m<\x1B[31m\x1B[33mstring\x1B[31m\x1B[33m,\x1B[31m \x1B[33mStringValues\x1B[31m\x1B[33m>\x1B[31m\x1B[33m,\x1B[31m config\x1B[33m?\x1B[31m\x1B[33m:\x1B[31m \x1B[33mPartial\x1B[31m\x1B[33m<\x1B[31m\x1B[33mRest\x1B[31m\x1B[33m.\x1B[31m\x1B[33mConfig\x1B[31m\x1B[33m>\x1B[31m) \x1B[33m=>\x1B[31m\n' +
    ' \x1B[90m    |\x1B[31m                              \x1B[31m\x1B[1m^\x1B[22m\x1B[1m\x1B[31m\n' +
    ' \x1B[90m 24 |\x1B[31m     \x1B[36mthis\x1B[31m\x1B[33m.\x1B[31mrestService\x1B[33m.\x1B[31mrequest\x1B[33m<\x1B[31m\x1B[33many\x1B[31m\x1B[33m,\x1B[31m \x1B[33mBillFileProcessDto\x1B[31m\x1B[33m>\x1B[31m({\n' +
    " \x1B[90m 25 |\x1B[31m       method\x1B[33m:\x1B[31m \x1B[32m'POST'\x1B[31m\x1B[33m,\x1B[31m\n" +
    " \x1B[90m 26 |\x1B[31m       url\x1B[33m:\x1B[31m \x1B[32m'/api/app/bill-file-processes/create-with-ocr'\x1B[31m\x1B[33m,\x1B[31m\x1B[0m\x1B[39m\x1B[22m",
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

Node.js v22.11.0

@maliming I have shared source code with you via email

@maliming

The impersonation issue I have solved. The issue I want to ask is "In Settings > Feature management, child feature is displayed on the same level as parent feature"

v8.2.3

v8.3.2

@maliming Please give me the document link

@maliming I tried your way but still get error 400

@maliming Thanks. "Login with this tenant" was displayed.

In Settings > Feature management, child feature is displayed on the same level as parent feature

Is it the bug?

• ABP Framework version: v8.3.2
• UI Type: Angular
• Database System: EF Core (MySQL.)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

In 8.3.2, there are 2 issues compared to 8.2.3

• In Sass > Tenants: "Login with this tenant" menu is not displayed
• In Settings > Feature management, child feature is displayed on the same level as parent feature

v8.2.3

v8.3.2

v8.2.3

v8.3.2

In 8.3.2, there are 2 issues compared to 8.2.3

• In Sass > Tenants: "Login with this tenant" menu is not displayed
• In Settings > Feature management, child feature is displayed on the same level as parent feature

v8.2.3

v8.3.2

v8.2.3

v8.3.2

@maliming I use ABP's built-in login completely. AuthServer is a separate project. Where can I change to achieve my desired result?