FIO-8354: fallback to passing response in argument if response.body is undefined #101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to Jira Ticket
https://formio.atlassian.net/browse/FIO-8354
Description
What changed?
Changed the events emitted by Formio to fallback to passing the response object to emit argument if response.body is undefined. This allows for clients using this api to handle these events based on the data in the response object.
I chose this solution because it allows for backwards compatibility by keeping response.body as a possible argument in the emit function
Breaking Changes / Backwards Compatibility
None
Dependencies
N/A
How has this PR been tested?
manually tested
Checklist: