Lines 25-65javascript
25 return ILayerCompatDetails?.supportedFeatures.has(feature) ?? false;
30var DataStoreMessageType;
31(function (DataStoreMessageType) {
32 // Creates a new channel
33 DataStoreMessageType["Attach"] = "attach";
34 DataStoreMessageType["ChannelOp"] = "op";
35})(DataStoreMessageType || (exports.DataStoreMessageType = DataStoreMessageType = {}));
37 * The common URL prefix used by legacy DDS type strings.
38 * Factories originally used full URLs (e.g. `"https://graph.microsoft.com/types/map"`);
39 * new factories use only the trailing path segment (e.g. `"map"`).
41 * Support for reading both formats was added in 2.92.0.
43 * This is encoded using base64 to avoid replacement of URL-like values that we have seen some reverse proxies perform.
44 * The value at runtime is "https://graph.microsoft.com/types/".
46const legacyTypeUrlPrefix = atob("aHR0cHM6Ly9ncmFwaC5taWNyb3NvZnQuY29tL3R5cGVzLw==");
47/**
HighBase64 Obscured Url
Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/dataStoreRuntime.jsView on unpkg · L45 48 * Wraps an {@link ISharedObjectRegistry} to transparently redirect legacy URL-based DDS type
49 * strings to the factories registered under the corresponding short-name path segment.
51 * When a lookup by the full URL fails, this wrapper retries using only the portion of the URL
52 * after `"https://graph.microsoft.com/types/"`. This allows old documents whose summaries
53 * contain URL-based type strings to be loaded against a registry built with the current
54 * short-name factory types.
57 * See {@link legacyTypeUrlPrefix} for details on old vs. new formats
59class LegacyTypeAwareRegistry {
64 let factory = this.base.get(name);
65 if (factory !== undefined) {