Throw proper JS errors #75
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…fix #25) This is for the sake of throwing errors that have stack traces, rather than strings which strip them for JS hosts. *Slight* API change in that setStyle now throws an error with a message, rather than returning a perfectly serialized JSON csl::StyleError. But that's an API for elsewhere; it would be called parseStyle, and it needs more features than setStyle does.
cormacrelf
changed the title
cormacrelf
added
A-wasm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #25.
Upgrades roxmltree while we're at it. Minor API change to setStyle(); it now throws rather than returning a perfectly serialized JSON error object.