The HTTP status, which is useful for differentiating success responses with data from those without.This use of 200 and 304 response codes is consistent with Remote Config's server implementation.
FetchResponseData.config
Defines the map of parameters returned as "entries" in the fetch response body.
Signature:
config?:{[key:string]:string;};
FetchResponseData.eTag
Defines the ETag response header value. Only defined for 200 and 304 responses.
This is consistent with Remote Config's server eTag implementation.
Signature:
eTag?:string;
FetchResponseData.status
The HTTP status, which is useful for differentiating success responses with data from those without.
This use of 200 and 304 response codes is consistent with Remote Config's server implementation.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[],[],null,["# FetchResponseData interface\n\nJSON-serializable representation of evaluated config values. This can be consumed by Remote Config web client SDKs.\n\n**Signature:** \n\n export interface FetchResponseData \n\nProperties\n----------\n\n| Property | Type | Description |\n|---------------------------------------------------------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [config](./firebase-admin.remote-config.fetchresponsedata.md#fetchresponsedataconfig) | { \\[key: string\\]: string; } | Defines the map of parameters returned as \"entries\" in the fetch response body. |\n| [eTag](./firebase-admin.remote-config.fetchresponsedata.md#fetchresponsedataetag) | string | Defines the ETag response header value. Only defined for 200 and 304 responses.This is consistent with Remote Config's server eTag implementation. |\n| [status](./firebase-admin.remote-config.fetchresponsedata.md#fetchresponsedatastatus) | number | The HTTP status, which is useful for differentiating success responses with data from those without.This use of 200 and 304 response codes is consistent with Remote Config's server implementation. |\n\nFetchResponseData.config\n------------------------\n\nDefines the map of parameters returned as \"entries\" in the fetch response body.\n\n**Signature:** \n\n config?: {\n [key: string]: string;\n };\n\nFetchResponseData.eTag\n----------------------\n\nDefines the ETag response header value. Only defined for 200 and 304 responses.\n\nThis is consistent with Remote Config's server eTag implementation.\n\n**Signature:** \n\n eTag?: string;\n\nFetchResponseData.status\n------------------------\n\nThe HTTP status, which is useful for differentiating success responses with data from those without.\n\nThis use of 200 and 304 response codes is consistent with Remote Config's server implementation.\n\n**Signature:** \n\n status: number;"]]