Clearly document "final" nature of Redirect finisher
It happens quite often that users create form definitions like this:
# ... finishers: - identifier: Redirect # ... - identifier: EmailToReceiver # ...
EmailToReceiver will never be executed since the
Redirect finisher terminates the current (HTTP) request immediately.
We should take some countermeasures to avoid this situation or at least give hints that a form definition like this will not give the expected results:
- Update the docs to warn about this in the section about finishers in general and for the
Redirectfinisher in particular
- Automatically add the
Redirectfinisher to the end in the form editor GUI and keep it there even on finisher redordering
- Refactor the code to actually execute the finisher only at the end of the request after all other finishers (this might require new API since 3rd party code will need this too)
- Show and/or log a warning if such a form is rendered (this covers hand-written form definitions)