Skip to content

Move and rename Sentry constants

Miguel Rincon requested to merge mrincon-sentry-constants into master

What does this MR do and why?

This change refactors our Sentry constants so they can be reused.

It also renames one of them to use the naming as newer versions of Sentry

I've split this change into different MRs, to make it easier to review:

Remove unusable Sentry feature flag (!104231 - merged) about to be merged!
Move and rename Sentry constants (!104247 - merged) you are here
Install two versions of Sentry Client SDK (!102790 - merged) the big one!

Screenshots or screen recordings

NA

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Miguel Rincon

Merge request reports