Naresh Bhatia

@FredyC, thanks for your insights. I am failing to understand how Context would help in this case. While an `onError` can pass the error to a context provider that will...

Thanks, @FredyC, that does give me a better "context" (pun intended) :-)

I know this is in the v5 roadmap, but is there a temporary workaround? Currently my graphql schema has ```graphql scalar DateTime ``` This generarates ```typescript export type Scalars =...

Ok, figured it out. Had to add a `config.scalars` in the preset itself: ```typescript import type { CodegenConfig } from '@graphql-codegen/cli'; const config: CodegenConfig = { schema: './src/gql/**.graphql', documents: ['src/**/*.{ts,tsx}'],...

I am also stuck on this issue. Not only is this an issue with email, but anytime I define a format which is optional. For example: var constraints = {...

Re-reading the docs, I found this: > Changelog - 0.11.0 - Breaking: The presence validator no longer allows empty and whitespace only strings per default. This behaviour can be modified...

Walking through the validate.js code I am arriving at the same conclusion as @ajenkins-kyr. The error we are getting has nothing to do with the `presence` validator. That validator is...

@ajenkins-kyr thanks for the workaround. Downgrading now.

Thanks @irudoy, I will give that a try. In the meanwhile, I was thinking if it would be better if the presence validator should be considered "special" and not run...

@ansman I am sure you are very busy. Can you give us some idea on when you will be active again on this project/issue? Thanks again for this great library.