Skip to content

Conversation

@sjdemartini
Copy link
Collaborator

@sjdemartini sjdemartini commented Jul 8, 2023

Fixes #1428 (after the change merged in #1421)

This should improve backwards compatibility, fixing issues in downstream packages (notably graphene-django-cud
tOgg1/graphene-django-cud#109, and also graphene-django-extras, both of which depended on
graphene_django.compat.JSONField). I've tested this in my downstream project and confirmed it resolved issues in both of those packages.

Fixes #1428

This should improve backwards compatibility, fixing issues in downstream
packages (notably graphene-django-cud
tOgg1/graphene-django-cud#109, and also
graphene-django-extras, both of which depended on
`graphene_django.compat.JSONField`).
@sjdemartini
Copy link
Collaborator Author

@firaskafri any chance you could take a look and see about merging this? Just a one-line change to fix backwards incompatibility. This is blocking my team from upgrading past 3.1.1 (and seemingly others like #1428). Thanks!

@firaskafri firaskafri self-requested a review July 18, 2023 12:11
@firaskafri firaskafri merged commit cd43022 into main Jul 18, 2023
@firaskafri firaskafri deleted the support-jsonfield-for-backwards-compat branch July 18, 2023 12:11
superlevure pushed a commit to loft-orbital/graphene-django that referenced this pull request Jul 19, 2023
)

Fixes graphql-python#1428

This should improve backwards compatibility, fixing issues in downstream
packages (notably graphene-django-cud
tOgg1/graphene-django-cud#109, and also
graphene-django-extras, both of which depended on
`graphene_django.compat.JSONField`).

Co-authored-by: Steven DeMartini <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Critical] Breaking change in patch release

5 participants