The Rust SDK appears to be missing the general scope attributes model required by the SDK develop docs. sentry-core::Scope currently exposes tags, extras, contexts, and user data, but not first-class scope attributes such as setAttribute, setAttributes, and removeAttribute, nor storage for typed scope attributes.
The shared scopes/attributes spec in getsentry/sentry-docs makes this normative: the Scopes spec says users MUST be able to attach attributes to any scope, and the Attributes spec says SDKs MUST provide dedicated methods for setting and removing them. The changelog dates this requirement to scopes spec 1.10.0 / attributes spec 1.2.0 (2025-11-03), with additional precedence and removal rules in attributes spec 1.3.0 (2025-11-11). Please add the underlying scope storage and public API in sentry-core, including typed values and non-breaking room for units, aligned with the spec.
The Rust SDK appears to be missing the general scope attributes model required by the SDK develop docs.
sentry-core::Scopecurrently exposes tags, extras, contexts, and user data, but not first-class scope attributes such assetAttribute,setAttributes, andremoveAttribute, nor storage for typed scope attributes.The shared scopes/attributes spec in
getsentry/sentry-docsmakes this normative: the Scopes spec says users MUST be able to attach attributes to any scope, and the Attributes spec says SDKs MUST provide dedicated methods for setting and removing them. The changelog dates this requirement to scopes spec 1.10.0 / attributes spec 1.2.0 (2025-11-03), with additional precedence and removal rules in attributes spec 1.3.0 (2025-11-11). Please add the underlying scope storage and public API insentry-core, including typed values and non-breaking room for units, aligned with the spec.