#7703 adding deprecations to release notes

[nathanglover]

Closes #7703

Adding the detail_route and list_route deprecations to the 3.10.x release notes. Let me know if I need to update the format at all.

[auvipy]

this is good addition i believe

[xordoquy]

Hi, thanks for the contribution.

Could you rename the link as [gh6687] and add [gh6687]: https://github.com/encode/django-rest-framework/issues/6687 around the bottom of the page in the 3.10 link section please ?

[nathanglover]

Sure thing. Completed in the most recent commit.

[Syntaf]

Thanks for taking the reigns on getting this PR done @nathanglover

Another breaking change I found relates to https://github.com/encode/django-rest-framework/pull/6659/files , which fixes a bug but causes None values to be ran through a fields validation and not short-circuted.

Essentially, if you're currently overriding to_internal_value on a base serializer class and handling the case where not field.source_attrs and validated_value is None, DRF versions after 3.9.X will break this fix.

Example:

class BaseModelSerializer(serializers.ModelSerializer):
  def to_internal_value(self, data):
    # ...
    for field in fields:
      # ...
      try:
          validated_value = field.run_validation(primitive_value)
          if validate_method is not None:
              validated_value = validate_method(validated_value)
      except ValidationError as exc:
          errors[field.field_name] = exc.detail
      except DjangoValidationError as exc:
          errors[field.field_name] = list(exc.messages)
      except SkipField:
          pass
      else:
          if not field.source_attrs and validated_value is None:
            # custom solution to correctly set field
          else:
            set_value(ret, field.source_attrs, validated_value)

Although it took me quite awhile to understand why this broke for us, it's a pretty deep edge case that's arguably our fault for toying with DRF internals.

Even so, if you all agree, I might recommend we change:

• Fix nullable fields with source="*"

To

• Fix nullable fields with source="*"

  Possible backwards compatibility break if you were previously relying on these fields to skip validation when receiving None, you will need to override your field's to_internal_value to short-circuit values of None to avoid any validation rules

I can submit a follow-up PR for this if needed

[tomchristie]

Looks good thanks @nathanglover.