Always defer to explicit overrides. · Issue #4198 · encode/django-rest-framework (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

Some of these may already be covered, but we should make sure that all the following are satisfied:

• If a user declares a field explicitly, but also includes it in extra_kwargs then warn/error.
• If a user declares a field explicitly, but also includes it in read_only_fields then warn/error.
• Don't allow get_uniqueness_extra_kwargs to override a declared field.
• Don't allow get_uniqueness_extra_kwargs to override a flag that has been set in extra_kwargs.
• If a serializer field has a default, then ensure that uniqueness validators use that for empty, rather than forcing required=True