getsentry / getsentry/sentry-ruby
Cleanup initialize/close behavior to prevent initialized? checks everywhere
Open
Refactoring
Ruby
Task
- Dominant language
- Ruby
- Stars
- 987
- Forks
- 541
- Avg merge
- 17h 40m
- Merged PRs (30d)
- 19
Description
And perhaps we should implement a better version of `close` and `Sentry.initialize?` 🤔
Specifically:
- We don't erase hub variables, `@background_worker` and `@session_flusher`
- `Sentry.initialize?` is backed by a simple boolean state that's changed by `Sentry.ini` and `Sentry.close`.
We would still need `Sentry.initialize?` in some places to stop some actions after the SDK is closed, but we don't need it for preventing`nil` value anymore, which is getting out of hand IMO.
_Originally posted by @st0012 in https://github.com/getsentry/sentry-ruby/pull/2084#discussion_r1308034537_
Contributor guide
Assessment
This issue has not been assessed yet.