v2.4.0

[jkimbo]

Release notes:

---

Changelog

Some great new features and lots of bugfixes in this release. A massive thanks to all the contributors that helped out! This release will probably be the last one before v3 (see #705)

New features

• Add support for write_only fields in SerializerMutation (Add support for write_only fields in SerializerMutation #555)
• Enhanced support for proxy models (Adds enhanced support for proxy models. #603)
• Add support for filterset_class meta parameter (Add support for filterset_class meta parameter #600)
• Add watch option to graphql_schema management command (Add watch option to graphql_schema #656)
• Add convert_choices_to_enum option on DjangoObjectType Meta class (Add convert_choices_to_enum option on DjangoObjectType Meta class #674)
• Add option CAMELCASE_ERRORS to camel case field names in DRF errors (Apply camel case converter to field names in DRF errors #514 and Adds documentation to CAMELCASE_ERRORS setting #689)
• Mark content of ManyTo* relationships as NonNull (Enforce NonNull for returned related Sets and their content #690)
• Alias only_fields as fields and exclude_fields as exclude (Alias only_fields as fields and exclude_fields as exclude #691)

Bugfixes

• Stop enforcing csrf checks in GraphQLTestCase (Stop enforcing csrf checks in GraphQLTestCase #658)
• Correctly propagate help_text as description for many-to-* relations (Correctly propagate help_text as description for many-to-* relations #579)
• Fix Django manager check in DjangoConnectionField (which was preventing prefetch_related optimisations from working) (Fix manager check in DjangoConnectionField #693)
• Remove duplicate ErrorType (Remove duplicate ErrorType #701)
• Ensure correct filter types for DjangoFilterConnectionFields (Bugfix: Correct filter types for DjangoFilterConnectionFields #682)
• Fix error of multiple inputs with the same type. When using same serializer. (Fix error of multiple inputs with the same type. When using same seri… #530)

Full changelog: v2.3.1...v2.4.0

[phalt]

Is this okay to go into master? I thought we had some code in master that was only for v3 launch?

[jkimbo]

@phalt I don't think there is anything in master that should be in v3. Travis is still testing python v2 so there shouldn't be any breaking changes.

[phalt]

🚢