Opened 12 years ago
Closed 12 years ago
#19847 closed New feature (wontfix)
add a "step_failure" method on WizardView
| Reported by: | mothsART | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.formtools | Version: | dev |
| Severity: | Normal | Keywords: | validate wizardview log |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
A little patch for a method i like using : "step_failure".
Goal: If you want catch all "invalid post" in a wizard forms.
For me, is a good way to log and stats a wizard in production.
Log failure bring me some indications : if a field validation is too complex, if design of form isn't user friendly etc.
This diff is minimmalist and a first suggestion. I'm open too talk about...
(in fact, that will bring API heavier...)
To see it : got to my pull request : https://github.com/django/django/pull/734
Change History (3)
comment:1 by , 12 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:2 by , 12 years ago
sorry, i work exclusively with a the .gitignore rule "*~"...
No ugly "views.py~ here: https://github.com/mothsART/django/commit/0428dde4e35410c9b5ad9b06d2c8c0981948f8c0
comment:3 by , 12 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
This is rather domain-specific; I don't think it warrants inclusion in Django.
I'm going to put this into DDN state pending an opinion from someone more familiar with the form wizard; I've never used it.