Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update debugging.mdx #1928

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update debugging.mdx #1928

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bfc7aa1
Update debugging.mdx
tore-statsig Aug 21, 2024
db1d093
Merge branch 'main' into tore-statsig-patch-22
tore-statsig Nov 7, 2024
9526f34
Update debugging.mdx
tore-statsig Nov 7, 2024
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
8 changes: 4 additions & 4 deletions docs/sdks/debugging.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,9 @@ When debugging why a certain user got a certain value, there are a number of too
- `Error`: an unknown error has occurred, and was logged to statsig servers
- `Error:NoClient`: No client was found in StatsigContext. Likely a call to a Statsig hook outside of the StatsigProvider. (js-client-only)
- `NetworkNotModified`: the network response came back, but the cached values were already up to date for this user
</TabItem>
<TabItem value="client-new" label="Client SDKs (New)">
- `NoValues`: The sdk was initialized, but there were no values in the cache for the user (and nothing fetched from the network). Commonly caused by calling `initializeSync` rather than waiting for `initializeAsync`
- `Loading`: Initialize was called, but the sdk is still waiting for the network request to resolve with updated values. You should `await` initialization before issuing checks

Newer versions of the sdk will contain two tags: one regarding the initialization state of the sdk, and the other qualifying different sources for that value.

So in addition to the reasons above, you may have:
Expand All @@ -68,8 +69,7 @@ When debugging why a certain user got a certain value, there are a number of too
- `LocalOverride`: from an override set locally on the SDK via an override API
- `Unrecognized`: the sdk was initialized, but this config did not exist in the set of values
- `Uninitialized`: the sdk was not yet successfully initialized
</TabItem>
<TabItem value="server-new" label="Server SDKS (New)">

In newer server SDKs, the reasons will be a combination of initialization source and evaluation reason:
**Initialization Source**
- `Network`: fetched at SDK initialization time from the network
Expand Down
Loading