Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix #1811: take limit_choices_to into account with FK #6371

Merged
merged 6 commits into from Jan 8, 2019
Merged

Fix #1811: take limit_choices_to into account with FK #6371

merged 6 commits into from Jan 8, 2019

Commits on Dec 20, 2018

  1. Fix issue1811: take limit_choices_to into account with FK

    Adrien Brunet committed Dec 20, 2018
    Copy the full SHA
    2d48dd4 View commit details
    Browse the repository at this point in the history

Commits on Dec 21, 2018

  1. Issue 1811: Add tests to illustrate issue

    Adrien Brunet committed Dec 21, 2018
    Copy the full SHA
    3f95d60 View commit details
    Browse the repository at this point in the history

  2. Filter queryset only if limit_choices_to exists

    Adrien Brunet committed Dec 21, 2018
    Copy the full SHA
    ca9dcdf View commit details
    Browse the repository at this point in the history

  3. Move test_relations_with_limited_querysets file within test_relations_pk

    Adrien Brunet committed Dec 21, 2018
    Copy the full SHA
    a66e8ac View commit details
    Browse the repository at this point in the history

Commits on Jan 8, 2019

  1. move limit_choices_to logic from relations.py to utils/field_mapping.py

    Adrien Brunet committed Jan 8, 2019
    Copy the full SHA
    7954c03 View commit details
    Browse the repository at this point in the history

  2. move limit_choices_to above other check to avoid conflicts

    Adrien Brunet committed Jan 8, 2019
    Copy the full SHA
    7fb879c View commit details
    Browse the repository at this point in the history