Rami Chowdhury

What behavior would you expect here? Note that as far as I know constraints are not supported in GraphQL -- https://github.com/APIs-guru/graphql-constraints-spec is all I could find and that's just a...

@daviddaskell thanks for this! I am not using `graphene_pydantic` any more at my work so not running into issues like this! I agree, `not field.allow_none` does seem to be the...

> 0.1.0 fork going as well until the Graphene 3 release happens with all the dependent libraries. That's right, currently 0.2.0 only supports Graphene 3. I'd welcome any changes that...

@dima-dmytruk23 in #73 where you brought this up, you mention a few specific cases. I am having trouble understanding what you need, and why these code changes are necessary for...

@dima-dmytruk23 thank you for the example! I've been looking into it and from what I can see, the input query turns into a `UserUpdateInput`, which is when the default values...

@dima-dmytruk23 it seems to me that if you are able to fix it with a change to `graphql-core` you should submit a PR there. As you said, if you used...

@dima-dmytruk23 if you have fixes for these issues it's definitely worth making a PR!

It looks like this `discriminator` behavior is new in Pydantic 1.9 -- there appear to be a few new features that we don't currently support, including this. The way to...

@MaximZemskov Yep, right now `graphene-pydantic` doesn't correctly account for the `alias` value on a Field; since this might involve changing the way attributes are looked up, it might be a...

@MaximZemskov any of us would be very happy to help you with anything you need :smile: