CreateUpdateView view class

[adi.andreias@…]

I think it makes sense to have a Class-based view for both updating and creating model objects.

BaseUpdateView and BaseCreateView differ by just two lines, one in get() and one in post():
​https://github.com/django/django/blob/1.7b4/django/views/generic/edit.py#L218
​https://github.com/django/django/blob/1.7b4/django/views/generic/edit.py#L195

A CreateUpdateView view would distinguish between create and update based on a slug, pk or similar (configurable?) parameter in url.

There are situations where the view class contains a lot of code logic (like a secondary formset, ajax requests handled along with regular requests, etc.) and having separate classes for create and update would result in duplicate code.

I also think this is a common pattern and deserves to be added to Django core.

[adi.andreias@…]

a working code draft (alpha version)

[Aymeric Augustin]

I'm a bit skeptical. Django already gets criticized for providing too many generic views.

[anonymous]

No need for this to be in core.

[Sasha Romijn]

Assuming, as you say, that the only difference is those two lines, that would also mean it is trivial to create this yourself: use a BaseUpdateView based class, and override get_object() in your class to return None whenever you want it to behave as a create view, instead of an update view. That will not introduce any code duplication.

I'm closing wontfix, as I then consider this to be something that is trivial to do, by design, outside of Django core.