Class-based generic views
— at Version 8
| Reported by: |
jkocherhans |
Owned by: |
nobody |
|
Component:
|
Generic views
|
Version:
|
|
|
Severity:
|
|
Keywords:
|
|
|
Cc:
|
Daniel Duan, floguy@…, David Larlet, Carl Meyer, Jannis Leidel, sciyoshi@…, vbmendes@…, anossov@…, mjmalone@…, taavi@…, narma.nsk@…, Oliver Beattie, Aaron C. de Bruyn, Jari Pennanen, brian@…, ssteinerX@…, drbob@…, ben@…, Alexander Koshelev, Chris Chambers, Brandon Konkle, Henrique Romano
|
Triage Stage:
|
Accepted
|
|
Has patch:
|
yes
|
Needs documentation:
|
yes
|
|
Needs tests:
|
no
|
Patch needs improvement:
|
no
|
|
Easy pickings:
|
no
|
UI/UX:
|
no
|
Rewrite generic view to be class based, but leave the existing generic views as-is for now.
Change History
(12)
| Needs documentation: |
set
|
| Needs tests: |
set
|
| Triage Stage: |
Unreviewed → Design decision needed
|
| Needs tests: |
unset
|
| Triage Stage: |
Design decision needed → Accepted
|
| Description: |
modified (diff)
|
| Summary: |
Class-based generic create/update/delete views → Class-based generic views
|
This ticket refs #3639 use newforms in generic create_update view