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

Add a test command #28

Merged
merged 1 commit into from
Aug 7, 2018
Merged

Add a test command #28

merged 1 commit into from
Aug 7, 2018

Conversation

rullzer
Copy link
Collaborator

@rullzer rullzer commented Aug 6, 2018

Fixes #27

Signed-off-by: Roeland Jago Douma [email protected]

Copy link
Owner

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

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

Thanks for looking into this!

@@ -5,7 +5,7 @@
<name>Sentry</name>
<summary>Sentry client</summary>
<description>A Sentry integration that sends unhandled exceptions to a Sentry instance to aggregate application crashes. You either have to set up your own Sentry instance or use your sentry.io account. See the admin documentation for how to configure this app.</description>
<version>3.0.0</version>
Copy link
Owner

Choose a reason for hiding this comment

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

This should be a minor version bump according to semver.

public function execute(InputInterface $input, OutputInterface $output) {
try {
throw new \Exception('This is a sentry test exception!');
} catch (\Exception $e) {
Copy link
Owner

Choose a reason for hiding this comment

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

Since you're catching the exception every time, wouldn't it just make sense to directly log it? Or does that make any difference for the report (stack trace missing or whatsoever)?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah the trace is a bit neater this way.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Really? Because the trace is generated on the new \Exception() and thus should not be much different, or am I totally wrong?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@MorrisJobke it is because it is still on my list to have some options to the command as well. So you get test with the log levels and all that.

@ChristophWurst ChristophWurst added this to the 3.1.0 milestone Aug 7, 2018
Fixes #27

Signed-off-by: Roeland Jago Douma <[email protected]>
@rullzer rullzer force-pushed the feature/27/add_test_command branch from e2559cb to 20107e0 Compare August 7, 2018 06:30
Copy link
Owner

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

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

Thanks 🚀

@ChristophWurst ChristophWurst merged commit b4e419e into master Aug 7, 2018
@ChristophWurst ChristophWurst deleted the feature/27/add_test_command branch August 7, 2018 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants