Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

formatedCreatedAt in fetchTickets return new DateTime #72

Open
winnie80 opened this issue Jul 25, 2023 · 1 comment
Open

formatedCreatedAt in fetchTickets return new DateTime #72

winnie80 opened this issue Jul 25, 2023 · 1 comment
Labels
Bug Something isn't working

Comments

@winnie80
Copy link

Description
I found out whenever list of all tickets is requested, there is formatedCreatedAt return with odd value.
I keep getting (almost) the same result "01-01-1970 15:16am".
The only think that changed was the time at the end of formatedCreatedAt.
At first I thought "api-bundle" could not returning proper "created at" date time value from database.
But oddly enough, it can when I requested to view single ticket, I get proper createdAt and updatedAt value.

How to reproduce
by requesting to /api/v1/tickets
check within "tickets" list , all formatedCreatedAt value started with "01-01-1970"

Possible Solution
at this point i'm not sure, yet
probably because of Webkul\UVDesk\ApiBundle\API\Tickets:objectSerializer
notice this line 920 = $object->formatedCreatedAt = new \Datetime;
probably should use correct value from $object->createdAt , with proper formatting
or just return $object->createdAt and let the frontend change it formatting according what it needs.

Can anyone please help me? thanks in advance

@komal-sh-27
Copy link

@winnie80

We have checked this issue and we will tried to fix this issue. It will be reflected in the future release.

Thanks for your time and patience!!!

Thanks and Regards
Uvdesk Team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants