Stefan

Yes, I hadn't realized DateTime wasn't a default type when trying this. Is there documentation on where we implement custom types in `neo4j-graphql`? Repro for NPE: Dockerfile ``` FROM neo4j:latest...

We originally considered ISO dates (js example below) but will probably switch to unix timestamps. ``` const DateTimeScalar = new GraphQLScalarType({ name: "DateTime", description: "DateTime scalar type", parseValue(value: string) {...

Cool, I'll try it. Will this support writing custom resolvers? Hoping to work around #84 with a custom JSONType.

Ah, I misunderstood. Simple conversions might be a nice future approach. But keeping current behaviour and coercing non-primitive types into JSON I think would go a very long way.

For the sake of an example, with this schema type Release { id: ID! @unique title: String! createdAt: String! } type QueryType { getit: String @cypher(statement: "MATCH (r {id: 'x87n6d'})...

I was going to submit an issue in google but saw [yours](https://github.com/google/diff-match-patch/issues/39) , thanks. If google is happy with status quo, I'd propose option 2 as the one that can...

@wilsonvolker this is a great find, thanks! This query works now, but still the sitemap config gives back this error. Have you encountered it too? ``` Error: Page array from...

[Here](https://stackoverflow.com/a/73400749/1827442)'s how I got the overall sitemap working again. I think the issue here is that people get stuck on the `siteUrl` error masking the real issue and don't easily...

Does this help? (no custom plugin) https://stackoverflow.com/questions/67242212/gatsby-cant-find-client-routes-when-using-gatsby-plugin-react-i18next/69905274#69905274

@PangYiMing do you have a situation in which the existing behavior is required? Even if there is one, unless it's the most pervasive, I think it should not be called...