Add missing DropTargetMoniter type arguments

[equt]

This should allow cases like

react-dnd/packages/examples-hooks/src/01-dustbin/copy-or-move/Dustbin.tsx

Line 40 in e8bd643

collect: (monitor: any) => ({

to have type inference.

[equt]

Wait, is this a bug of GitHub?

[darthtrevino]

Oh that's weird, it nuked your branch? I merged some other PRs that were pending. It looks like this is a bot you installed on your fork?

[equt]

Yes, I installed the pull bot for synchronizing my forks, it basically does a simple fetch and force push I guess. Well, it's my bad to use it globally.

But the problem here is why the CI is triggered? This is my first pull request in this repository, so it should be blocked. Did you trigger that @darthtrevino?

---

I've recovered it, and it still gets blocked. So either this bot has contributed to this repo, or there is a potential bug to bypass the maintainer's approval.

[darthtrevino]

Hey @equt - I'm considering this one. It definitely improves the typings, but it compromises the development ergonomics. A developer would now have to specify 3 generic parameters explicitly when using useDrag(). I've tried to make that implicit as possible, which is why I've left those generic args out, but I'm open to reconsidering.

[equt]

The actual reason for this pull request is that I found the generic arguments for the monitor of DragSourceHookSpec is provided

react-dnd/packages/react-dnd/src/hooks/types.ts

Lines 85 to 87 in ce9dd69

	collect?: (
	monitor: DragSourceMonitor<DragObject, DropResult>,
	) => CollectedProps

However the one for the DropTargetHookSpec is not

react-dnd/packages/react-dnd/src/hooks/types.ts

Line 137 in ce9dd69

collect?: (monitor: DropTargetMonitor) => CollectedProps

[mifozski]

Why not also provide the arguments to the rest of the DropTargetHookSpec's monitor usages? Like in drop, hover signatures, etc.

[darthtrevino]

These types have been incorporated in #3300; thanks everyone!