You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'm trying to implement Django Wizard's conditional view in my project but I can't. Whenever I access my form page, I receive the error: RecursionError: maximum recursion depth exceeded
.
I investigated what is generating this error with ipdb and found that the WizardView.get_cleaned_data_for_step(step) method
is causing the problem.
I would like help to know if I implemented the feature correctly or if this is a bug.
NT. I want it to work as follows:
In the PessoaForm form there is a checkbox field where my user must select one of two options: PF or PJ. If he selects PF then the next form displayed should be the PessoaFisicaForm and if he selects the PJ option, then the PessoaJuridicaForm form should be displayed.
These are my forms
This is my view
and this is the callable that you create according to the documentation guidance
Error generated
The text was updated successfully, but these errors were encountered:
Hello! I'm trying to implement Django Wizard's conditional view in my project but I can't. Whenever I access my form page, I receive the error:
RecursionError: maximum recursion depth exceeded
.
I investigated what is generating this error with ipdb and found that the
WizardView.get_cleaned_data_for_step(step) method
is causing the problem.
I would like help to know if I implemented the feature correctly or if this is a bug.
NT. I want it to work as follows:
In the PessoaForm form there is a checkbox field where my user must select one of two options: PF or PJ. If he selects PF then the next form displayed should be the PessoaFisicaForm and if he selects the PJ option, then the PessoaJuridicaForm form should be displayed.
These are my forms
This is my view
and this is the callable that you create according to the documentation guidance
Error generated
The text was updated successfully, but these errors were encountered: