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

[2.0] Do not return error id if we know we did not send the error #671

Closed
wants to merge 2 commits into from

Conversation

stayallive
Copy link
Collaborator

If we know we did not sent the error to a Sentry server we should not return the error id or keep track of that event as the last event.

@stayallive stayallive requested review from HazAT and Jean85 October 12, 2018 10:40
Copy link
Collaborator

@ste93cry ste93cry left a comment

Choose a reason for hiding this comment

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

We should change all the capture* methods of the Client class to return string|null

@@ -237,6 +237,19 @@ public function testGetLastEvent()
$this->assertSame($lastEvent, $client->getLastEvent());
}

public function testGetLastEventEmptyIfNotSent()
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please rename testGetLastEventEmptyIfNotSent to testGetLastEventReturnsNullIfLastEventWasNotSent

@HazAT
Copy link
Member

HazAT commented Nov 16, 2018

Closing this, this is already in 2.0, we always return ?string now.

@HazAT HazAT closed this Nov 16, 2018
@ste93cry ste93cry deleted the do-not-set-last-error-when-not-sending branch November 16, 2018 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants