Regeneration of Poco about dotnet-starter-kit

[iammukeshm]

I even tried to delete the ApiClient class and generated it again via CLI. Not able to replicate this issue. Seems to work fine.

[kallievz]

found it... nevermind

[kallievz]

I cannot get the script to run. Seems Client.Infrastructure project is outdated

[iammukeshm]

@kallievz , i usually navigate to src\apps\blazor\infrastructure\Api and run the following.

nswag run ./nswag.json

Make sure that your WebAPI is up and running. The webapi should be running on the port specified in the nswag.json file.

[kallievz]

from cmd?

[iammukeshm]

yes @kallievz . make sure you have the nswag cli installed.

[kallievz]

awesome, thanks

[iammukeshm]

please close this ticket if you think the issue is resolved.

[kallievz]

regen worked, but now I cannot login. I can see the token Api being called, but not navigating to "/"

[kallievz]

[kallievz]

hi @iammukeshm
I regen'd the poco using cmd. But seems the json tags are different, login seems to hit the api, but that is where it stops.

I regenerated now again, and compared to the pre changed version. JsonProperty names is different, Could this be causing the issue? Setting i need to change on Nswag.Json file? Sorry all the questions, i am used to Asp.Net webforms dev, not the new sparkly generators.

[kallievz]

Got it to go camelCase by changing :
// Add framework services.
builder.Services
.AddRazorPages().AddJsonOptions(options => options.JsonSerializerOptions.PropertyNamingPolicy = null);

to :
// Add framework services.
builder.Services
.AddRazorPages().AddJsonOptions(options => options.JsonSerializerOptions.PropertyNamingPolicy = System.Text.Json.JsonNamingPolicy.CamelCase);

Not sure why, i was not looking forward to creating json annotation on all classes.