expandContentFilter
Prior to serialization into the query syntax for the backing APIs, we first expand Filters
Filter's can express their intent in a very terse form, but to ensure consistent structures we expand them into their more verbose form.
i.e. title: "Water"
expands into title: { any: ["Water"]}
- "well known" type values are expanded
- i.e.
type: "$storymap"
expands into twosubFilter
entries
- i.e.
- Fields defined as
string | string[] | MatchOptions
will be converted to aMatchOptions
- RelativeDate fields are converted to DateRange
Parameters
Parameter | Type | Default | Notes |
---|---|---|---|
filter Required | Filter<"content"> |
Returns
Property | Type | Notes |
---|---|---|
Optional | IMatchOptions | |
Optional | IDateRange<number> | |
Optional | IMatchOptions | |
Optional | IMatchOptions | |
Optional | IMatchOptions | |
Optional | IDateRange<number> | |
Optional | IMatchOptions | |
Optional | IMatchOptions | |
Optional | IContentFilter[] | |
Optional | IMatchOptions | |
Optional | string | |
Optional | IMatchOptions | |
Optional | IMatchOptions | |
Optional | IMatchOptions |
Function defined in common/src/search/content-utils.ts:307