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.

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

Fix for declared fields being processed when not in fields list #1702

Conversation

matthewhegarty
Copy link
Contributor

@matthewhegarty matthewhegarty commented Dec 4, 2023

Problem

Closes #1693

There needs to be an extra check that any declared fields are also listed in the fields list if it exists.

@matthewhegarty matthewhegarty changed the base branch from main to release-4 December 4, 2023 15:42
@matthewhegarty matthewhegarty marked this pull request as ready for review December 4, 2023 17:40
Copy link

@pokken-magic pokken-magic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@matthewhegarty matthewhegarty merged commit fb2951f into django-import-export:release-4 Dec 10, 2023
13 checks passed
@matthewhegarty matthewhegarty deleted the issue-1693-declared-fields-issue branch December 10, 2023 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Declared fields are still imported/exported even if they are not defined in Meta.fields
2 participants