Activities of "pkouame"

@alper - on FileProviders I updated my project file manually to let it compile - I was just letting you guys know - I'm on visual studio code on the mac

on gulp - how do you suggest I fix this problem ? Isn't this a problem with your installer ?

UPDATE:

after 3.1.0 release abp switch-to-stable generates the same gulp install error but since mine is installed via yarn gulpfile.js is processed correctly as long as my version of gulp-cli is updated to CLI version 2.3.0. Just to let you guys know (don't know where to report these problems - so just doing so here if it helps anyone). Also FileProviders still needs to be manually updated to 3.1.6 or else aspnet-core doesn't build.

after abp switch-to-preview (abp cli updated to 3.1.0-rc.4 ) on a 3.0.5 project, I get this error regarding an npm gulp installation:

[13:09:58 INF] Checking installed npm global packages... [13:10:00 INF] Installing gulp... npm ERR! code EEXIST npm ERR! syscall symlink npm ERR! path ../lib/node_modules/gulp/bin/gulp.js npm ERR! dest /usr/local/bin/gulp npm ERR! errno -17 npm ERR! EEXIST: file already exists, symlink '../lib/node_modules/gulp/bin/gulp.js' -> '/usr/local/bin/gulp' npm ERR! File exists: /usr/local/bin/gulp npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly.

my version of gulp and gulp cli (installed via yarn) are :

gulp -v [13:20:03] CLI version 3.9.1 [13:20:03] Local version 4.0.2

A little later during the switch, I get :

[12:34:12 INF] Running Gulp on /Users/me/dev/aqua/abp-pro/v300/Kuvu.Track/aspnet-core/src/Kuvu.Track.HttpApi.Host/ [12:34:13] Using gulpfile ~/dev/aqua/abp-pro/v300/Kuvu.Track/aspnet-core/src/Kuvu.Track.HttpApi.Host/gulpfile.js /Users/me/.config/yarn/global/node_modules/gulp/bin/gulp.js:129 gulpInst.start.apply(gulpInst, toRun); ^

TypeError: Cannot read property 'apply' of undefined at /Users/me/.config/yarn/global/node_modules/gulp/bin/gulp.js:129:20 at processTicksAndRejections (internal/process/task_queues.js:79:11)

UPDATE: In addition to the above. the back-end does not start until I upgrade my Microsoft.Extensions.FileProviders.Embedded from 3.1.5 to 3.1.6 in Domain.Shared

<PackageReference Include="Microsoft.Extensions.FileProviders.Embedded" Version="3.1.6" />

Anything to worry about?

Thanks - will the angular version be available soon ? (Devextreme angular => 20.1.7)

Especially a datagrid sample with both client and server side rendering

Ok - just to be clear

• you are reporting that the "vendorLookup" versus "vendor-lookup" route naming issue has been fixed in 3.0.3 and the convention is %%np-entity-name-camelcase%%-lookup. At the time this was reported the server route name was still "vendorLookup"
• I didn't experience the second primary key issue you mentioned. But I'll assume that has been fixed also.

Thank yoiu

Ok - I will check out 3.0.3 - thank you.

Did I assume correctly that the api should be called %%np-entity-name-camelcase%% Lookup instead of %%np-entity-name-camelcase%%-lookup? What is your naming convention?

My template fix works but I want to make sure before I used it across my other tables...

Also - how to get rid of that garballed template above (would you know how that happened?)

Any news on this case?

Anybody there?

Ok - looks like this is another Template Error (arghhhh) - there were two consequences

1- build error and migration interrruption 2- bad api name

[Route("%%np-entity-name-camelcase%%Lookup")] instead of

[Route("%%np-entity-name-camelcase%%-lookup")]

not sure what the intent was - here's my edit:

ALSO - what is this in my template folder and how can I fix it :

steps to reproduce:

• create an entity Vendor with a int primary key
• create an VendorTest with a navigation property to Vendor

Controllers/VendorTests/VendorTestController.cs(16,56): error CS0738: 'VendorTestController' does not implement interface member 'IVendorTestAppService.GetVendorLookupAsync(LookupRequestDto)'. 'VendorTestController.GetVendorLookupAsync(LookupRequestDto)' cannot implement 'IVendorTestAppService.GetVendorLookupAsync(LookupRequestDto)' because it does not have the matching return type of 'Task<PagedResultDto<LookupDto<int?>>>'. [/Users/me/dev/aqua/abp-pro/v290/skipjack/Skipj.Track/aspnet-core/src/Skipj.Track.HttpApi/Skipj.Track.HttpApi.csproj] 0 Warning(s) 1 Error(s)

as you can see below ... in visual studio code VendorTestController.cs returns:

[HttpGet] [Route("vendor-lookup")] public Task<PagedResultDto<LookupDto<Guid?>>> GetVendorLookupAsync(LookupRequestDto input) { return _vendorTestAppService.GetVendorLookupAsync(input); }

    when it should be Task<PagedResultDto<LookupDto<int?>>
    
    

Please help - this is a showstopper

abp v2.9.0 abp suite v2.9.0 brand new solution created with 2.9 already re-installed abp suite from scratch

• yes, then the "Generating CRUD Page" needs to change then
• how is the regex used?
• Does Required work correctly - left unchecked the UI still attempts to validate on submit. I thought it was supposed to mean dot not require a value and do not validate . Os is it setting min/max length that triggers validation no matter what (at least on angular side)

EDIT: after debugging noticed that it's a server side error - fields NOT marked required in the CreateDto get flagged when the UI passes an empty string...

my solution is angular/core on 2.9.0