Files
klz-cables.com/.pnpm-store/v10/files/91/87283efb8e62ddd71687830840985953027b11509eae90245b043c0f82d085f335ea6689e7e1b566bbdaf28773385b3340c4cd73b4053456f81d48d4ad801a
Marc Mintel 5397309103
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 20s
Build & Deploy / 🧪 QA (push) Failing after 34s
Build & Deploy / 🏗️ Build (push) Has started running
Build & Deploy / 🚀 Deploy (push) Has been cancelled
Build & Deploy / 🧪 Smoke Test (push) Has been cancelled
Build & Deploy / ⚡ Lighthouse (push) Has been cancelled
Build & Deploy / 🔔 Notify (push) Has been cancelled
fix(products): fix breadcrumbs and product filtering (backport from main)
2026-02-24 16:04:21 +01:00

24 lines
1.0 KiB
Plaintext

import type { Field } from 'payload';
import { GraphQLInputObjectType } from 'graphql';
type Args = {
fields: Field[];
name: string;
parentName: string;
};
/** This does as the function name suggests. It builds a where GraphQL input type
* for all the fields which are passed to the function.
* Each field has different operators which may be valid for a where input type.
* For example, a text field may have a "contains" operator, but a number field
* may not.
*
* buildWhereInputType is similar to buildObjectType and operates
* on a field basis with a few distinct differences.
*
* 1. Everything needs to be a GraphQLInputObjectType or scalar / enum
* 2. Relationships, groups, repeaters and flex content are not
* directly searchable. Instead, we need to build a chained pathname
* using dot notation so MongoDB can properly search nested paths.
*/
export declare const buildWhereInputType: ({ name, fields, parentName }: Args) => GraphQLInputObjectType;
export {};
//# sourceMappingURL=buildWhereInputType.d.ts.map