$or operator for filtering

[jfcieslak]

There seems to be no defined way to use $or operators in filters. Can you suggest the proper way of adding a resolver for such case? I imagine that the resulting graphQL schema should look sth. like this:

input filterInput {
    OR: [filterInput!]! 
}

[nodkz]

Good feature request.
Added in 3.1.0

All filter arguments now get AND and OR fields, where you may provide complex nested sub-queries. Affected filter arguments in the following resolvers: findOne, findMany, updateOne, updateMany, removeOne, removeMany.

Live Demo

Current test case:

graphql-compose-mongoose/src/__tests__/github-issues-test.js

Lines 156 to 190 in 6abef5f

	it('#93 $or, $and operator for filtering', async () => {
	schemaComposer.rootQuery().addFields({
	users: UserTC.getResolver('findMany'),
	});
	const schema = schemaComposer.buildSchema();
	await UserModel.create({
	_id: '100000000000000000000301',
	name: 'User301',
	age: 301,
	});
	await UserModel.create({
	_id: '100000000000000000000302',
	name: 'User302',
	age: 302,
	gender: 'male',
	});
	await UserModel.create({
	_id: '100000000000000000000303',
	name: 'User303',
	age: 302,
	gender: 'female',
	});
	const res = await graphql.graphql(
	schema,
	`
	{
	users(filter: { OR: [{ age: 301 }, { AND: [{ gender: male }, { age: 302 }] }] }) {
	name
	}
	}
	`
	);
	expect(res).toEqual({ data: { users: [{ name: 'User301' }, { name: 'User302' }] } });
	});

[jfcieslak]

WOW. That was a fast turnaround for a feature request. Thanks!

[bakuzan]

I gave this a try and it works great when using field filters, but custom filter arguments, ones added with resolver.addFilterArg, aren't being picked up when used inside an OR/AND

[nodkz]

@bakuzan I opened a new issue with your problem: #95 Lets discuss it there separately.