Jonathan Kim

> We should consider all options, but the API should be backward compatible, to not cause another turmoil in the GraphQL-Python ecoystem, and the code and API should not deviate...

This looks like an issue in sqlalchemy not in graphql

@dionyself looks like a [graphene-django](https://github.com/graphql-python/graphene-django) issue but since you're here I'll try and help. I think the issue is that graphene-django tries to convert the `DurationField` to a `Float` graphql...

@Cito I agree, option 1 makes the most sense.

@GinTR1k the plan is to merge `aiohttp-graphql` into graphql-server-core and release it as v3. See: https://github.com/graphql-python/graphql-server-core/issues/44 and https://github.com/graphql-python/graphql-server-core/issues/34

@brabeji yes the graphql-core v3 (#249) will resolve this issue. Graphql-core v3 is going to be [graphql-core-next](https://github.com/graphql-python/graphql-core-next) which is a complete rewrite bringing it up to feature parity with graphql.js

@sergey-komissarov this doesn't look like a bug because you're trying to pass the string `null` to the JSON parser and so it's going to error out. If you have no...

@sergey-komissarov my apologies you're absolutely right. It looks like the bug is here: https://github.com/graphql-python/graphql-core/blob/fa4eeda36029680205e20059379e89189b946032/graphql/utils/is_valid_value.py#L77-L79 Because `json.loads("null")` returns `None` it's tripping up the validation and throwing the error. Unfortunately I can't...

> @patrick91 @jkimbo is this proposal favored? @aryaniyaps what proposal do you mean? If you mean whether the class docstrings should be used as GraphQL descriptions: my opinion is that...

FYI I think this proposal should still be implemented: https://github.com/strawberry-graphql/strawberry/issues/872