Hi @geoff.thorpe - I'm glad to hear you're using neo4j-graphql.js! Yes, both of these should be addressed when we add support for the filter parameter in neo4j-graphql.js. There is an ongoing discussion in this Github issue. Would you mind adding your use cases (ideally with examples) so we can be sure they are addressed when we add the feature?
As for a workaround, you could add a custom @cypher directive query to your schema that implements the date range / filtering logic. Something like: