Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make it clear that all exposed functions mentioned on this page should be exposed on the scope?

Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,15 @@
title: Feature Flags
description: Guidelines for tracking feature flag evaluations — scope storage, span attributes, the add_feature_flag API, and third-party integrations.
spec_id: sdk/foundations/client/integrations/feature-flags
spec_version: 1.0.1
spec_version: 1.0.2
spec_status: stable
spec_depends_on:
- id: sdk/foundations/client/integrations
version: ">=1.0.0"
spec_changelog:
- version: 1.0.2
date: 2026-07-07
summary: Added `clear_feature_flags` scope API
- version: 1.0.1
date: 2026-06-05
summary: Fixed `add_feature_flag` API specifying unsupported feature flag value types
Expand Down Expand Up @@ -47,6 +50,14 @@ If an SDK supports feature flags it MUST expose a function `add_feature_flag` wh

</SpecSection>

<SpecSection id="clear-feature-flags" status="stable" since="1.0.2">

### The `clear_feature_flags` API

SDKs **MAY** expose a `clear_feature_flags` function on the scope. When called, it **MUST** remove all feature flag evaluations stored on the current scope. It **MUST NOT** affect feature flags on parent or sibling scopes.

</SpecSection>

<SpecSection id="feature-flag-integrations" status="stable" since="1.0.0">

### Integrations
Expand Down
Loading