Type Alias GameDealsQuery
GameDealsQuery: {
aaa?: boolean;
atLow?: boolean;
cursor?: string;
developer?: string;
earlyAccess?: boolean;
endingWithinHours?: number;
featured?: boolean;
freeWeekend?: boolean;
genre?: string;
kind?: string;
limit?: number;
maxPriceCents?: number;
minDiscount?: number;
minRating?: number;
publisher?: string;
q?: string;
sort?: "updated" | "discount" | "ending";
store?: string;
tag?: string;
tier?: string;
}
Type declaration
Optionalaaa?: boolean
OptionalatLow?: boolean
Optionalcursor?: string
Optionaldeveloper?: string
OptionalearlyAccess?: boolean
OptionalendingWithinHours?: number
Optionalfeatured?: boolean
OptionalfreeWeekend?: boolean
Optionalgenre?: string
Optionalkind?: string
Optionallimit?: number
OptionalmaxPriceCents?: number
OptionalminDiscount?: number
OptionalminRating?: number
Optionalpublisher?: string
Optionalq?: string
Optionalsort?: "updated" | "discount" | "ending"
Optionalstore?: string
Optionaltag?: string
Optionaltier?: string
UNVERIFIED UPSTREAM - confirm before a UI offers this as a filter.
getDealsis a passthrough: every field here is serialised straight onto the Games API request, and Noti does not implement the filtering. If that API ignores unknown params, a caller passing this gets UNFILTERED results that look filtered, which is worse than having no filter at all.The parameter is accepted and forwarded by the Noti route; that is all it guarantees.