Skip to content

chore: updating identify code documentation #129

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

Merged
merged 2 commits into from
May 30, 2025
Merged

chore: updating identify code documentation #129

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
74a8f8b
chore: updating identify code documentation
louis-launchdarkly May 29, 2025
79c750d
chore: updating wording of identify code documentation
abarker-launchdarkly May 30, 2025
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
7 changes: 7 additions & 0 deletions typings.d.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1071,6 +1071,13 @@ export interface LDPlugin {
* Changing the current context also causes all feature flag values to be reloaded. Until that has
* finished, calls to {@link variation} will still return flag values for the previous context. You can
* use a callback or a Promise to determine when the new flag values are available.
*
* It is possible that the identify call fails. In that case, when using a callback, the callback will receive
* an error value. While the SDK will continue to function, developer will need to be aware that
* calls to {@link variation} will still return flag values for the previous context.
*
* When using a promise, it is important that you handle the rejection case;
* otherwise it will become an unhandled Promise rejection, which is a serious error on some platforms.
*
* @param context
* The context properties. Must contain at least the `key` property.
Expand Down