feat: nuxt, captureError method, perevent multiple sending #111
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
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.
This PR introduces several updated needed for @hawk.so/nuxt integration.
captureErrorpublic method.Hawk Nuxt SDK uses own error capturing method, but will uses Hawk Javascript for processing and sending.
__hawk-processed__to prevent multiple sending.SDK may have own error capturing method and normally re-trow error down. This update is needed to handle this case.
Nuxt addons types added
Sanitizer moved from adding to upper level to simplify adding adding
Utils moved from
utils.tsto/utils/