feat(custom-dnd-backend): Add props to override react-dnd backend #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My last one for now, I promise 😉
I realise this is a bit of a power user feature, but I was in need of using the react-dnd's TouchBackend instead of MultiBackend+HTML5toTouch. The reason is I'm using sound effects and the HTML5 drags for some reason don't count as user interaction, so modern browsers will disallow audio playing if it's not triggered by user interaction. TouchBackend (with mouse enabled) works perfectly fine for me, even though it has a note about being buggy and it is recognized as user interaction.
Anyway, only using TouchBackend might not be for everyone, so for this PR I decided to add a prop (or 2 actually) to be able to swap out the backend for a different one.
Usage:
Of course, leaving out these props will keep the existing behavior of using MultiBackend+ HTML5toTouch.