Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow custom client to be passed #17

Merged
merged 3 commits into from
Jun 5, 2019
Merged

Allow custom client to be passed #17

merged 3 commits into from
Jun 5, 2019

Conversation

guischdi
Copy link
Contributor

@guischdi guischdi commented Jun 4, 2019

fixes #16 by allowing

to pass Sentry instance to plugin

Ensures that the needed functions are present (by using a new joi schema), if a custom Sentry client is passed.

CC: @jardakotesovec

@guischdi guischdi added the enhancement New feature or request label Jun 4, 2019
@jardakotesovec
Copy link
Contributor

@guischdi This looks great. Should do the trick for me. Thanks!

Copy link
Contributor

@fiws fiws left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few validation things, i noticed. Everything else is 👍

schema.js Show resolved Hide resolved
schema.js Show resolved Hide resolved
@fiws fiws merged commit 46b5b3f into master Jun 5, 2019
@fiws fiws deleted the custom-client branch June 5, 2019 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Option to use Sentry also outside of the plugin
3 participants