-
Notifications
You must be signed in to change notification settings - Fork 179
Preparations for stable release #73
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
Conversation
…e services configuration to non-deprecated values
…red before loading a console command
This is no longer WIP, requesting reviews! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just quick question to make sure we're not losing functionality but otherwise lgtm
->prototype('scalar')->end() | ||
->defaultValue(array('%kernel.root_dir%/..')) | ||
->end() | ||
->arrayNode('excluded_app_paths') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these (and the others) are still configured somewhere yeah?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I've already released a gradual upgrade path in the 0.8.3 release, see the changelog here and the related PR, #68.
Basically those where the deprecated, old config values, that were copied under options
, since they are all direct Sentry client options. In here I'm just dropping the deprecated ones, the new ones are already in place.
This PR tries to accomplish a bunch of improvements and cleanup for the upcoming 1.0 release.
Currently it does:
src/Sentry/SentryBundle
->src/
)sentry.options
if it's a\Raven_Client
optionExceptionListener
; also the Client is no longer an optional argumentSentryExtensionTest
This is till a WIP, I will update this list as I will go on.