* Support realtime updates for Rollouts * Map optimization and lint * update changeset
3.5 KiB
Project: /docs/reference/js/_project.yaml Book: /docs/reference/_book.yaml page_type: reference
{% comment %} DO NOT EDIT THIS FILE! This is generated by the JS SDK team, and any local changes will be overwritten. Changes should be made in the source code at https://github.com/firebase/firebase-js-sdk {% endcomment %}
FetchResponse interface
Defines a successful response (200 or 304).
Modeled after the native `Response` interface, but simplified for Remote Config's use case.
Signature:
export interface FetchResponse
Properties
| Property | Type | Description |
|---|---|---|
| config | FirebaseRemoteConfigObject | Defines the map of parameters returned as "entries" in the fetch response body. Only defined for 200 responses. |
| eTag | string | Defines the ETag response header value. Only defined for 200 and 304 responses. |
| experiments | FirebaseExperimentDescription[] | Metadata for A/B testing and Remote Config Rollout experiments. |
| rollouts | FirebaseRolloutMetadata[] | Metadata for Remote Config Rollout experiments. |
| status | number | The HTTP status, which is useful for differentiating success responses with data from those without. The Remote Config client is modeled after the native Disambiguation: the fetch response returns a legacy "state" value that is redundant with the HTTP status code. The former is normalized into the latter. |
| templateVersion | number | The version number of the config template fetched from the server. |
FetchResponse.config
Defines the map of parameters returned as "entries" in the fetch response body.
Only defined for 200 responses.
Signature:
config?: FirebaseRemoteConfigObject;
FetchResponse.eTag
Defines the ETag response header value.
Only defined for 200 and 304 responses.
Signature:
eTag?: string;
FetchResponse.experiments
Metadata for A/B testing and Remote Config Rollout experiments.
Only defined for 200 responses.
Signature:
experiments?: FirebaseExperimentDescription[];
FetchResponse.rollouts
Metadata for Remote Config Rollout experiments.
Only defined for 200 responses.
Signature:
rollouts?: FirebaseRolloutMetadata[];
FetchResponse.status
The HTTP status, which is useful for differentiating success responses with data from those without.
The Remote Config client is modeled after the native `Fetch` interface, so HTTP status is first-class.
Disambiguation: the fetch response returns a legacy "state" value that is redundant with the HTTP status code. The former is normalized into the latter.
Signature:
status: number;
FetchResponse.templateVersion
The version number of the config template fetched from the server.
Signature:
templateVersion?: number;