Add a convenient wrapper class with defaults to simplify setup #124
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
added 4 commits
January 29, 2020 14:47
…details from the top-level
… and sync sample apps, hiding the HTTP client and transport from the top-level usage
…TP client from the RaygunClientFactory
samuel-holt
changed the title
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.
Overview
During testing and documentation, I noticed the RaygunClient setup process was quite verbose and complicated - which could potentially be a barrier. I've created a wrapper class which will take care of building the HTTP client and transport, and just requires an API key (similar to the old API). This also hides the base URI and reduces the number of lines of code required to get set up.