-
Notifications
You must be signed in to change notification settings - Fork 7
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
Bundle? #19
Comments
Thanks for your feedback! Really appreciate it! I have considered doing a bundle with but I am running out of time these days. Actually it's possible to use the official symfony bundle now that it is allowed to disable the exception listener but it would not be as customizable of course. Also, I still need to check if it could do everything the symfony guide do in a reasonable way. Would you be interested to share the bundle you did? I could set up a private repo and we could then work the details out of it. |
Yes, I will move the bundle from our private gitlab to github soon, will leave a message here. Might take a few days, since I'm not able to work right now. |
Sorry for the delay, this corona-stuff is really messing with my ability to do extra-work ;-) |
Thanks! |
Any updates here? |
The official Sentry Bundle should adopt the behavior describe in the next major. see getsentry/sentry-symfony#337 |
Closing as this is gonna be fixed in the official Sentry Symfony bundle |
Thanks for your great work!
Have you ever considered bundling your config from the symfony-guide into a bundle?
We are using it the factory code 1:1, and have placed it in a bundle with some configurations, and with configurable listeners (for console, request, user).
Works like a charm.
The text was updated successfully, but these errors were encountered: