Server returns deprecated format of 'createdAt' timestamps
See original GitHub issuePlayground somehow displays another representation of the timestamps then expected.
With this query:
query { message(id: "1") { text createdAt } }
I get this as result:
{ "data": { "message": { "text": "Published the Road to learn React", "createdAt": "1539693730039" } } }
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:12 (6 by maintainers)
Top Results From Across the Web
php8.1 - Deprecated Functionality: DateTime()
We use the following code that worked perfectly on php7.4, but we get a deprecated error on php8.
Read more >12.7 Date and Time Functions
TIMESTAMP (), With a single argument, this function returns the date or ... Time zones are specified as described in Section 5.1.13, “MySQL...
Read more >The Definitive Guide to DateTime Manipulation
If you don't pass anything to the Date constructor, the date object returned contains the current date and time. You can then format...
Read more >Date - JavaScript - MDN Web Docs - Mozilla
Chrome Edge
Date Full support. Chrome1. Toggle history Full support. Edge12. Toggle hist...
@@toPrimitive Full support. Chrome47. Toggle history Full support. Edge15. Toggle hist...
Date() constructor...
Read more >Timestamp | JavaScript SDK | Firebase JavaScript API reference
Reference for Timestamp. ... isEqual. isEqual ( other : Timestamp ) : boolean. Returns true if this Timestamp is equal to the provided...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

It´s called
graphql-iso-dateyou can install it withnpm install --save graphql-iso-dateoryarn add graphql-iso-dateand here is a link to their repository.
Replacing
[Sequelize.Op.lt]: cursor,by[Sequelize.Op.lt]: new Date(Number(cursor)).toISOString(),hotfixes the issue for testing with playground.For a real fix I would prefer a custom date scalar (there are already packages for that) since dates are something very common to deal with when handling data.