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

Avoid recommending replacing image/document models entirely #6624

Merged
merged 1 commit into from Dec 9, 2020

Conversation

kaedroho
Copy link
Contributor

@kaedroho kaedroho commented Dec 9, 2020

... when using the WAGTAILIMAGES_IMAGE_MODEL/WAGTAILDOCS_DOCUMENT_MODEL settings.

We can't really support this as we add new fields and methods to these base classes which all images/documents must support. If we did want to support swapping out the models entirely, every addition we make to the base models could be a breaking change.

... when using the ``WAGTAILIMAGES_IMAGE_MODEL``/``WAGTAILDOCS_DOCUMENT_MODEL`` settings.

We can't really support this as we add new fields and methods to these base classes which all images/documents must support. If we did want to support swapping out the models entirely, every addition we make to the base models could be a breaking change.
@squash-labs
Copy link

squash-labs bot commented Dec 9, 2020

Manage this branch in Squash

Test this branch here: https://kaedroho-patch-1-08qyb.squash.io

@gasman gasman merged commit 4565005 into master Dec 9, 2020
@kaedroho kaedroho deleted the kaedroho-patch-1 branch December 10, 2020 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants