f5034f74ca
Expanded homepage pins to support 2 types of input (if both are passed in, pinnedUrls take precedence): (1) pinnedUrls --> uses doResolveUris (resolve) (2) pinnedClaimIds --> uses doResolveClaimIds (claim_search) Instead of injecting the pinned URLs directly, we inject from `resolvedPinUris`, which will be blank until the uris are resolved, thus preventing it from being resolved individually from the tiles. There's additional complexity with the `claim_search` method, as the rest of the code deals with uris instead of IDs. Fortunately, it's all contained with `useResolvePins`, so removal would be easier when the batch `resolve` issue is fixed.
30 lines
576 B
JavaScript
30 lines
576 B
JavaScript
declare type HomepageObject = {
|
|
icon: string,
|
|
link: string,
|
|
options: any,
|
|
route: string,
|
|
title: string,
|
|
};
|
|
|
|
declare type HomepageData = {
|
|
[string]: HomepageObject,
|
|
default: any => any,
|
|
};
|
|
|
|
declare type RowDataItem = {
|
|
id: string,
|
|
title: any,
|
|
link?: string,
|
|
help?: any,
|
|
icon?: string,
|
|
extra?: any,
|
|
pinnedUrls?: Array<string>,
|
|
pinnedClaimIds?: Array<string>, // pinnedUrls takes precedence
|
|
options?: {
|
|
channelIds?: Array<string>,
|
|
limitClaimsPerChannel?: number,
|
|
pageSize?: number,
|
|
},
|
|
route?: string,
|
|
hideForUnauth?: boolean,
|
|
};
|