Date Issue on client application

[mark-mngoma]

I have been testing the sample dotnet project and notice that the client app has an issue is saving dates previous to the one inputted on the form but it works well with postman. Is the issue in this line of code: if (!employee.id) { const today = moment().startOf('day'); employee.hireDate = today; } in the employee-update component?

[mark-mngoma]

I chose 2020-09-18 but api response payload gives 2020-09-17

[nicolas63]

Our clients code is based on java version can you verify if the java application has the same bug ?

[mark-mngoma]

I have a java project running and it is fine, but I think the problem is within the dotnet client application neither java or dotnet server applications.

[nicolas63]

The dotnet client (angular) is exactly the same than java version. Which version of jhipster is on your java project?

[mark-mngoma]

They are not exactly. I am actually testing this project: https://github.com/jhipster/jhipster-sample-app-dotnetcore

[mark-mngoma]

The java project is running version 5.4.2, which is working fine.

[nicolas63]

This blueprint is base on jhipster 6.10.1

[mark-mngoma]

Yes it is, but the bug persists on this version as well as I am testing on the latest and it seems the date reverts a day back.

[nicolas63]

Ok i think is link to https://github.com/jhipster/generator-jhipster/issues/11740

[mark-mngoma]

This issue is not happening on the Java project, only the dotnet project.

[nicolas63]

Ok i will investigate this problem

[mark-mngoma]

Still an issue I am failing to resolve as I don't know whether the issue is how the date is parsed on the client application, because when I test on postman, everything works fine, so the issue is the client.

[nicolas63]

Can you give me more information i can't reproduce this on my machine, can you give me jdl / jhipster version / your machine os ?

[mark-mngoma]

It's this repo:https://github.com/jhipster/jhipster-sample-app-dotnetcore that I am running on the latest version of Windows 10 and also on docker.

[nicolas63]

you don't generate an application ? you use directly the sample ? ok can try to reproduce with the sample

[mark-mngoma]

Yes, I am using the sample project to reference the logic on the client application, especially when it comes to setting datepickers through moment.js as you're using it in the sample project.

[mark-mngoma]

I have a generated project, which I am referencing from the sample project.

[nicolas63]

Everything in the example is generated with the generator. But ok I will try again to reproduce.

Thanks for your feedback.

[mark-mngoma]

Sure, please just working in doing a form post on the client to see the issue as it doesn't occur when testing with swagger or postman.

[mark-mngoma]

Any field with datetime

[nicolas63]

I have try this but it's ok for me. Wich date format is on your os ?

[mark-mngoma]

Really? Does it not set to the date before? Like if you select 2020-06-04 then it persists as 2020-06-03?

My os datetime format is ddmmyyyy.

[nicolas63]

I have the same format. Can you try to generate an application with the latest version on the master ? ( you need to clone and call npm link )

[mark-mngoma]

Using the jhipster generator and the jdl for entities or the demo repo?

[nicolas63]

Generator and jdl or you can also use entity cli

[nicolas63]

git clone cd repo npm link jhipster --blueprints dotnetcore jhipster entity YourEntity

[mark-mngoma]

I am still getting the same issue, I am testing with entity employee, field hireDate

[mark-mngoma]

I did everything here but I am still getting this issue. Please send me a screenshot of the process.

[mark-mngoma]

I am still receiving this issue on response payload it shows date as hireDate: 2020-09-22T22:00:00, but date chosen was: 2020-09-23T22:00:00

[mark-mngoma]

I am debugging and the timestamp is just being set at 22h00, I am not sure what config is handling this but it's on the client application, not the api.

[mark-mngoma]

It seems like this bug is some UTC parsing issue with Moment as it's happening with all the client applications from the dotnetcore generator.

[nicolas63]

sorry for the delay, yes it's possible that the error comes from moment.js and UTC

[mark-mngoma]

I am thoroughly reading the moment documentation but if you have an idea on fixing the bug please give me an update when possible.

[nicolas63]

in which timezone are you ?

[mark-mngoma]

SAST UTC+2

[nicolas63]

Can you try to add options.SerializerSettings.DateTimeZoneHandling = DateTimeZoneHandling.Utc; in newtonsoft options in MvcStartup.cs ?

[mark-mngoma]

I have added. Issue still persists as is

[mark-mngoma]

I am testing the Java project and it's doing the same thing. Any ideas of configuring moment() properly?

[mark-mngoma]

It's a weird issue, very difficult to debug where it's coming from.

[mark-mngoma]

But it is definitely an issue on client application parsing the date properly.

[nicolas63]

if the bug il also on the java version can you open an issue on https://github.com/jhipster/generator-jhipster ?

check before if the issue is not already open

[mark-mngoma]

I managed to get this fixed but it would be great for you to look at it and fix it for future releases.

[nicolas63]

@NtsikaMngoma how did you fix it ?

[mark-mngoma]

@NtsikaMngoma how did you fix it ? https://github.com/jhipster/generator-jhipster/issues/12577

[nicolas63]

Ok but we need to take open this issue while the other issue is not resolve

[mark-mngoma]

It's the same issue, should I close it or will you close it once resolved?

[mark-mngoma]

Please have a look at this issue as I am battling to figure it out: https://github.com/jhipster/jhipster-dotnetcore/issues/378