Graphene-django-crud

Changed

- Support multiple databases by dropping the transaction in mutations resolvers

Fixed

- FIX delete field and disconnect field do not exist in updateNestedInput

Breaking change:

- Normalize oderByInput with the other inputs, it is no longer a list of strings
- Need to use the resolver_hints decorator for the creation of computed fields

Changed

- Remove related_field in createNestedInput and updateNestedInput for
ManyToOneRel, OnetoOneField and OnetoOneRel fields

Added

- Improve sql performance with use only, select_related, prefetch_related
- Meta Parameter where_only_fields / where_exclude_fields, order_by_only_fields
/ order_by_exclude_fields
- add year, month, day, week_day parameters in the dateFilter
- add hour, minute, second parameters in the timeFilter

Fixed

- FIX WhereInput does not use related_query_name

Fixed

- FIX mutation errors are used by all exceptions without processing error
messages, now only ValidationError with message processing
- FIX a complex query can return several same instance
- FIX the createdField does not apply where input

Changed

- "WhereWithOperatorsInput" merge to "WhereInput" and keep operators
- Upgrade graphene-django dependency version to >= 2.8.0

Added

- Add django dependency to version >= 2.2
- Add getters 'WhereInputType', 'CreateInputType', UpdateInputType from
'GrapheneDjangoCrud' object
- Add possibility to extend the create and update input fields
- Add max_limit meta parameter for limit batchread request

Fixed

- Improve the stability of the relationship mutations

Changed

- Replace all "WhereUniqueInput" to "WhereInput"

Added

- Add "isnull" arg in "InputTypeFilter"

Fixed

- FIX error mutation with related foreign key
- FIX manytomanyfield dont have BatchReadField args
- FIX bad attribute for the related field whose related_name is not specified
- FIX error in mutation resolver with foreignKeyField not null
- FIX "InputTypeFilter" of FloatField, Datefield and TimeField is not generated