Graphene-django-plus

Latest version: v5.1

Safety actively analyzes 688126 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 11

2.2.2

* Fix a small issue with `get_node` optimizing the queryset twice

2.2.1

- Don't check for object permissions if there aren't any defined in the meta

2.2

* Call `check_object_permissions` again in `ModeType.get_node` so one extending it might implement some additional logic.

2.1

* Improve `CountableConnection.total_count` to use the already calculated `.length` if it exists to avoid an extra db query

2.0

All news here are _BREAKING CHANGES_ for anyone relying on the old behaviours. Most should not be affected!

* New `permissions_any` in both types and mutations to define if the general permissions should be checked by "all" (all permissions are given) or "any" (any permissions are given). Defaults to `True` (and thus is a breaking change comparing to the way it used to work)
* `graphene_django_plus.exceptions.PermissionDenied` now inherits from `django.core.exceptions.PermissionDenied` instead of trying to inherit from `graphql_jwt`'s
* Removal of `prefetch` from type. `graphene_django_optimizer` should already be doing that correctly those days.

1.4

* `ModelType.get_node` will preserve retrieve the result from the type's `get_queryset` when using `graphene-django-optimizer`. This may be a breaking change for someone relying on this wrong behaviour.

Page 7 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.