Add a common class-based delete view (including template)
All threads resolved!
All threads resolved!
Merge request reports
Activity
added part::backend part::frontend type::feature labels
mentioned in merge request AlekSIS-App-Alsijil!64 (merged)
- Resolved by Jonathan Weth
Also, should this take
reversion
into account? EIther by using it, or optionally using it, or at least documenting how to combine it with this view?As a general concept, features like permissions or versioning are included by mixins in class-based views, both documented in their home projects
django-rules
anddjango-reversion
.
added 1 commit
- 5f6a10e3 - Add warning to delete view to prevent wrong usage
added 3 commits
-
5f6a10e3...692a99f1 - 2 commits from branch
master
- 3ba2f310 - Merge branch 'master' into feature/base-delete-view
-
5f6a10e3...692a99f1 - 2 commits from branch
enabled an automatic merge when the pipeline for 3ba2f310 succeeds
mentioned in commit c0331a18
mentioned in merge request AlekSIS-App-LDAP!48 (merged)
Please register or sign in to reply