-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
render_wizard callback #277
Comments
@RobertAudi I had the same question today. We are solving the issue right now by doing the update first, performing our business logic and then calling render_wizard. However, this is not exactly ideal since it is saving the record twice. It does seem like it would be nice to have callbacks at least for the success case when calling render_wizard. |
I'm running into the same issue trying to render a flash based on whether or not the |
I've come up with the following solution. In the event of an error, you can call def update
@model.update(model_params)
if @model.errors.any?
# TODO: Your business logic goes here
render_step(step)
else
render_wizard(@model)
end
end |
When the
render_wizard
method is called with a resource it saves it, and then either redirects to the next step or re-renders the current step in case of errors.Looking at the code, it is impossible to perform actions based on the result of the save. One such example is flash messages, but this can be worked around using the
options
argument ofrender_wizard
.Another example that is impossible to solve at the moment is business logic after saving the resource.
At this point I don't know if this is a feature request or a question on how to solve this problem, but I would be surprised if I am the first person to bring this up. Is there a known solution or workaround to this problem?
The text was updated successfully, but these errors were encountered: