Changing notify to use xpcall with stacktrace on failure #230
+210
−141
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.
This makes debugging why your callback failed much easier especially if you are using other peoples libs/code
Below is an example of an intentionally injected hook and event failure. Before it only included the line it failed on instead of teh call trace section. Additionally it did not have the event\hook field before. This should allow for easier debugging of hooks especially that are failing in lower level, generic code
To test, add code that will intentionally fail and trigger the hooks. In this case, I added an addNextTurnHook hook and a onGameEntered event (each only had the hook/event which is why they are different hook/event) with a few layers of fns just to show the stack trace is working correctly
Then start a game (trigger onGameEntered failure), enter a mission and end turn (trigger nextTurnHook)