Bugs & Issues v4.1.X #626

108 Answer(s)

• 

  0

  dmeagor created 3 years ago

  Issue with hangfire after update from 4.0.2 to 4.1.0

  My developer has posted details here also. https://github.com/abpframework/abp/issues/7147

  Save Cancel
• 

  0

  dmeagor created 3 years ago

  @alper

  Regarding the suite updating issue above. I'm not entirelly sure what caused it but I can tell you that they were modules not applications. There were two modules, the first updated fine, the second just kept reporting success even though it hadn't done anything. Cli worked ok.

  Regarding the Anglar proxy issue, our dev said "It doesn't change the 'apiName' in the generated services. Even though it uses this parameter to generate them". He said it was a minor issue though.

  Save Cancel
• 

  0

  armanozak created 3 years ago

  Hi @dmeagor,

  The apiName property in generated services are collected from the remoteServiceName property of each module in the /api/abp/api-definition response. The response looks like this:

  {
    "modules": {
      "identityServer": {
        "rootPath": "identityServer",
        "remoteServiceName": "AbpIdentityServer",
        "controllers": { /* controller definitions here */ },
      },
      "types": { /* type definitions here */ }
  }
  

  The --api-name parameter, on the other hand, points to the setting in the environment.ts file we should use to fetch /api/abp/api-definition response from. This parameter is useful when building a module and is usually omitted or passed as default when developing apps.

  One helpful tip: You can make the CLI ask you questions by running abp generate-proxy --prompt. It then explains what each parameter is good for.

  Save Cancel
• 

  0

  dmeagor created 3 years ago

  @armanozak Thanks, I'll pass that along to the dev.

  Save Cancel
• 

  0

  AlderCove created 3 years ago

  @alper any update on this?

  @lwilbourn @rcalv002 I reproduced the issue. There's a problem generating the Angular code. Created an internal issue. Will be fixed in v4.0.1
  

  I have just updated abp cli and suite to 4.1.1, created a new solution but the CRUD Page Generator isn't generating Angular UI.

  I can see an issue in the Angular Schematics log file.

  0 verbose cli [ 0 verbose cli 'C:\Program Files\nodejs\node.exe', 0 verbose cli 'C:\Users\UserName\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js', 0 verbose cli 'exec', 0 verbose cli '--', 0 verbose cli 'C:/Users/UserName/Source/Repos/TestAngular/angular/.suite/schematics/node_modules/.bin/ng', 0 verbose cli 'g', 0 verbose cli '.suite/schematics/collection.json:entity', 0 verbose cli 'app-pro', 0 verbose cli 'TestAngular', 0 verbose cli 'C:/Users/UserName/Source/Repos/TestAngular/aspnet-core/.suite/entities/PeriodType.json' 0 verbose cli ] 1 info using npm@7.4.0 2 info using node@v12.14.1 3 timing config:load:defaults Completed in 1ms 4 timing config:load:file:C:\Users\UserName\AppData\Roaming\npm\node_modules\npm\npmrc Completed in 2ms 5 timing config:load:builtin Completed in 2ms 6 timing config:load:cli Completed in 3ms 7 timing config:load:env Completed in 0ms 8 timing config:load:file:C:\Users\UserName\Source\Repos\TestAngular\angular.npmrc Completed in 0ms 9 timing config:load:project Completed in 1ms 10 timing config:load:file:C:\Users\UserName.npmrc Completed in 1ms 11 timing config:load:user Completed in 1ms 12 timing config:load:file:C:\Users\UserName\AppData\Roaming\npm\etc\npmrc Completed in 0ms 13 timing config:load:global Completed in 0ms 14 timing config:load:cafile Completed in 0ms 15 timing config:load:validate Completed in 0ms 16 timing config:load:setUserAgent Completed in 0ms 17 timing config:load:setEnvs Completed in 1ms 18 timing config:load Completed in 10ms 19 verbose npm-session 46848984ec072eb7 20 timing npm:load Completed in 19ms 21 timing command:exec Completed in 6ms 22 verbose stack Error: ENOENT: no such file or directory, open 'C:\Users\UserName\Source\Repos\TestAngular\angular.suite\schematics\node_modules.bin\ng\package.json' 23 verbose cwd C:\Users\UserName\Source\Repos\TestAngular\angular 24 verbose Windows_NT 10.0.18363 25 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Users\UserName\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "exec" "--" "C:/Users/UserName/Source/Repos/TestAngular/angular/.suite/schematics/node_modules/.bin/ng" "g" ".suite/schematics/collection.json:entity" "app-pro" "TestAngular" "C:/Users/UserName/Source/Repos/TestAngular/aspnet-core/.suite/entities/PeriodType.json" 26 verbose node v12.14.1 27 verbose npm v7.4.0 28 error code ENOENT 29 error syscall open 30 error path C:/Users/UserName/Source/Repos/TestAngular/angular/.suite/schematics/node_modules/.bin/ng/package.json 31 error errno -4058 32 error enoent ENOENT: no such file or directory, open 'C:\Users\UserName\Source\Repos\TestAngular\angular.suite\schematics\node_modules.bin\ng\package.json' 33 error enoent This is related to npm not being able to find a file. 34 verbose exit -4058

  Save Cancel
• 

  0

  tomasz.lewandowski@neuca.pl created 3 years ago

  • ABP Framework version: v4.1.1
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Seperated (Angular): no
  • Steps to reproduce the issue:

  Hi, I found a bug in CRUD Generator for Angular or maybe proxy generator. When you created a solution with a dot in the name like this: and create simple entity:

  then generated angular proxy model looks like this: and I have build errors.

  When I don't use dots in the solution name then everything works fine and I have generated dto objects in angular project.

  Save Cancel
• 

  0

  armanozak created 3 years ago

  Hi tomasz.lewandowski@neuca.pl,

  Yes, there is a bug, but it isn't because of the dot in the solution name. The proxy generator tries to resolve any types with the keyword "System" in it. It apparently cannot resolve the types properly when the solution name ends with the word "System" (and has a dot in the solution name). ~~We will fix it quickly.~~ ~~There is an open PR for this now.~~ Fixed.

  Save Cancel
• 

  0

  alper created 3 years ago

  Support Team Director

  @AlderCove we couldn't reproduce it. can you create a new question, seems like it'll be being discussed (not to bother others)

  Save Cancel