getsentry / getsentry/sentry-ruby
Align SDK with docs regarding session update for dropped events
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 988
- Forks
- 542
- Avg merge
- 17h 40m
- Merged PRs (30d)
- 19
Description
### Description
We've updated the docs (https://github.com/getsentry/develop/pull/551) to explain how we would like to handle event filter order, updating of sessions for dropped events and sending of session updates. We should check if we're aligned and adapt if necessary. Here's the issue from the Java SDK where all of this started: https://github.com/getsentry/sentry-java/issues/1916
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked develop pull request and the originating sentry-java issue to understand the intended event-filter order, dropped-event session updates, and session-update sending behavior. Compare those requirements with the Ruby SDK, then verify that its behavior matches the documentation and adjust any discrepancies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100