You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: types/splitio.d.ts
-52Lines changed: 0 additions & 52 deletions
Original file line number
Diff line number
Diff line change
@@ -691,52 +691,6 @@ declare namespace SplitIO {
691
691
[statusinConsentStatus]: ConsentStatus;
692
692
};
693
693
}
694
-
/**
695
-
* Readiness Status interface. It represents the readiness state of an SDK client.
696
-
*/
697
-
interfaceReadinessStatus{
698
-
699
-
/**
700
-
* `isReady` indicates if the client has triggered an `SDK_READY` event and
701
-
* thus is ready to evaluate with cached data synchronized with the backend.
702
-
*/
703
-
isReady: boolean;
704
-
705
-
/**
706
-
* `isReadyFromCache` indicates if the client has triggered an `SDK_READY_FROM_CACHE` event and
707
-
* thus is ready to evaluate with cached data, although the data in cache might be stale, not synchronized with the backend.
708
-
*/
709
-
isReadyFromCache: boolean;
710
-
711
-
/**
712
-
* `isTimedout` indicates if the client has triggered an `SDK_READY_TIMED_OUT` event and is not ready to evaluate.
713
-
* In other words, `isTimedout` is equivalent to `hasTimedout && !isReady`.
714
-
*/
715
-
isTimedout: boolean;
716
-
717
-
/**
718
-
* `hasTimedout` indicates if the client has ever triggered an `SDK_READY_TIMED_OUT` event.
719
-
* It's meant to keep a reference that the SDK emitted a timeout at some point, not the current state.
720
-
*/
721
-
hasTimedout: boolean;
722
-
723
-
/**
724
-
* `isDestroyed` indicates if the client has been destroyed, i.e., `destroy` method has been called.
725
-
*/
726
-
isDestroyed: boolean;
727
-
728
-
/**
729
-
* `isOperational` indicates if the client can evaluate feature flags.
730
-
* In this state, `getTreatment` calls will not return `CONTROL` due to the SDK being unready or destroyed.
731
-
* It's equivalent to `isReadyFromCache && !isDestroyed`.
732
-
*/
733
-
isOperational: boolean;
734
-
735
-
/**
736
-
* `lastUpdate` indicates the timestamp of the most recent status event.
737
-
*/
738
-
lastUpdate: number;
739
-
}
740
694
/**
741
695
* Common API for entities that expose status handlers.
742
696
*/
@@ -745,12 +699,6 @@ declare namespace SplitIO {
745
699
* Constant object containing the SDK events for you to use.
746
700
*/
747
701
Event: EventConsts;
748
-
/**
749
-
* Gets the readiness status.
750
-
*
751
-
* @returns The current readiness status.
752
-
*/
753
-
getStatus(): ReadinessStatus;
754
702
/**
755
703
* Returns a promise that resolves once the SDK has finished synchronizing with the backend (`SDK_READY` event emitted) or rejected if the SDK has timedout (`SDK_READY_TIMED_OUT` event emitted).
756
704
* As it's meant to provide similar flexibility to the event approach, given that the SDK might be eventually ready after a timeout event, the `ready` method will return a resolved promise once the SDK is ready.
0 commit comments