Regarding the auto-response suggestions: I checked DbContext for duplicate lines although the entire solution compiles successfully so there are no compilation issues causing it. Furthermore, I have done a full re-install of ABP Suite (both Microsoft Store version and standalone installer) so this should've cleared the internal ABP Suite cache as well.
Hi Sumeyee, I've now sent over an example to your inbox. Thanks for taking the time to review our issue.
Hi, I am already on 9.2.0:
I will send over a sample of our project for you to see the reproduction on your end and reply here once I've done that. Thank you!
Hi Sumeyee, I've done a switch to stable on each the main project and subprojects so that they're all using ABP Volo packages of 9.2.0
I tried deleting the schematics folder in the .suite folder in the module project, rebuilt the solution in VS as well, and then clicked "save and generate" and the same error still occurs.
The package.json of the schematics still shows up as the following though:
"name": "@volo/abp.ng.suite",
"version": "9.2.0-rc.3",
Any way to get this on 9.2.0 instead of the rc.3 version? I also updated ABP Studio from 1.0.0 to 1.0.1 which was released just today (June 13).
Alternatively, is there a way I can privately send our project to see if you can reproduce the error on your side?
Just writing to follow up on the AI response that I've already tried deleting the .suite folder and re-generated the PurchaseOrder.json from scratch. The other steps don't apply yet as the error is occurring at generation step and not within the Angular project/output itself.
I just tried paring down the PurchaseOrder.json but the generation step still fails even with a single field in it.
Thanks, that should do the trick. I had an idea that customizing one of the templates would be necessary but for some reason I couldn't seem to isolate which one to edit.
Hi, I just created a project from scratch, upgraded to 9.2.0-rc.2, and then save and generated a new CRUD page with the generator (named WorkArea) and unfortunately wasn't able to reproduce the issue.
The following worked fine as expected when generated WorkArea in the MAIN project:
import { WorkAreaService } from '../../../proxy/work-areas/work-area.service'; (no controller in path)So it seems that there is something misconfigured perhaps from my older project based on an earlier 9.0.3 ABP version I think?
Workaround that seemed to work for me:
angular\.suite\schematics from the new project to my old project and deleted the generate-proxy.json from the src\proxy\ folder and it seems to be generating the path correctly now without the controllers in the path.
