Interface DomainList
interface DomainList {
domains: readonly DomainEntry[];
instructions: Instructions;
limits: Limits | null;
deprecated: boolean;
deprecationMessage: string;
sunsetDate: string | null;
serverCommit: string;
}
domains: readonly DomainEntry[];
instructions: Instructions;
limits: Limits | null;
deprecated: boolean;
deprecationMessage: string;
sunsetDate: string | null;
serverCommit: string;
}
Index
Properties
Readonlydomains
The domains this credential may name.
Readonlyinstructions
What the service asks the caller to do with them.
Readonlylimits
The bounds to enforce, or null when the service reported none.
Readonlydeprecated
deprecated: boolean
Whether the service considers this client out of date.
ReadonlydeprecationMessage
deprecationMessage: string
The service's own wording of the notice. Empty when there is none.
ReadonlysunsetDate
sunsetDate: string | null
When the deprecated thing stops working, as YYYY-MM-DD.
ReadonlyserverCommit
serverCommit: string
The server commit this response came from.
What MemoryOperations.listDomains returns.
Calling it is also how a client learns the caps it enforces locally, which is why Memco.connect calls it while verifying the connection. Until it has answered, every request is checked against structural rules only and the service decides the rest.
limitsisnullwhen the service reported none, and that means "check nothing" rather than "every cap is zero" — reading an absent message as zeros would reject every call before it was sent. A service that predates the field sends nothing at all, so this is the state to expect from an older one, not a malfunction.deprecateddoes not say whether it is the API version or this SDK build that is superseded, and is not meant to: onlydeprecationMessagecarries the remedy, so relay the message rather than inferring a cause from the flag. The SDK raises a process warning from the message rather than from the flag, once per distinct message, tagged with DEPRECATION_WARNING_NAME.Example