⚡ Improve find query performance and add adapterFactory with options

[dawidreedsy]

This code is taken from admin repo and simplified

[alecgibson]

Can we have a test for this please

[alecgibson]

While _id is pretty standard, uuid less so. I think we should make this configurable somehow, which also lets us change the Admin app without having to change this library every time we want to add a new field to this.

[dawidreedsy]

Test already exists

adminjs-mongoose/test/resource/find.spec.ts

Lines 22 to 33 in 9e80449

	it('searches by id', async () => {
	const users = await factory.createMany('user', 10)
	const resource = new Resource(User)
	const limit = 5
	const offset = 0
	const idFilters = new Filter({ _id: users[0]._id.toHexString() }, resource)
	const returnedItems = await resource.find(idFilters, { limit, offset })
	expect(returnedItems.length).toEqual(1)
	expect(returnedItems[0]).toBeInstanceOf(BaseRecord)
	})

[alecgibson]

This feels like a big departure from upstream. It's nice to keep as closely aligned as possible in case upstream changes.

I think I'd expect to configure this per-resource, probably by augmenting ResourceOptions (maybe set in properties?

[dawidreedsy]

I feel like this will do even bigger change especially in tests

[dawidreedsy]

We already diverged quite a bit from master as we use version 3.0.3 thay are already on version 4 which is ESM only

[alecgibson]

I'm beginning to wonder if we should jump the Admin app to ESM. It's relatively small, so might hopefully be one of the more painless apps to move

[dawidreedsy]

As discussed let's not move it to ESM as it not as simple as it looks.
We already diverged from admin js (version 4 actually do very similar to what i do), so let me know if you sitll insit on implementing it using this:

I think I'd expect to configure this per-resource, probably by augmenting ResourceOptions (maybe set in properties?

[alecgibson]

We've moved to ESM, so can you please rebase/rework on top of upstream?