feat: add context capture API - #1378
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
efccd51 to
c6716f7
Compare
c6716f7 to
5af8a98
Compare
5af8a98 to
de7d759
Compare
de7d759 to
545c0ef
Compare
545c0ef to
4997f79
Compare
4997f79 to
180fcc5
Compare
26a5f90 to
148a75b
Compare
148a75b to
066ed7c
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 066ed7c. Configure here.
066ed7c to
6cf3963
Compare
szokeasaurusrex
left a comment
szokeasaurusrex
left a comment
There was a problem hiding this comment.
In general the changes look good to me (though I am also not super familiar with everything being changed).
The one point that is unclear to me is what the context itself is meant to do, as the linked issues do not really describe it.
Is the new API documented somewhere in more detail? If yes, please link, if not, let's discuss it.
| return client.CaptureException(err, opts.hint, scope) | ||
| } | ||
|
|
||
| func (client *Client) processEvent(event *Event, scope *Scope, opts captureOptions) (*EventID, bool) { |
There was a problem hiding this comment.
l: What does the bool indicate here?
I think it would be worth adding a documentation comment to explain what the bool means
2 participants
Description
Issues
Changelog Entry Instructions
To add a custom changelog entry, uncomment the section above. Supports:
For more details: custom changelog entries
Reminders
feat:,fix:,ref:,meta:)