Add the option suppressRefError to getRootProps.

[yp]

Fixes #235.

What:
The option suppressRefError has been added to getRootProps to bypass the ref check when it erroneously raises an error.

Why:
As discussed in #235, a ref could be correctly forwarded to the root DOM element of a composite child but the ref check could still fail.
The new option allows to bypass such a check.

How:
A new optional argument of getRootProps has been introduced.
This argument must be an object and if it has the key suppressRefError and if the corresponding value evaluates to true the ref check is bypassed (but the check that getRootProps has been called is still performed).
The introduction of the second argument of getRootProps instead of using a key in the first argument is intentional in order to clarify that it is not a prop forwarded to the root component.

Checklist:

• Documentation
• Tests
• Ready to be merged
• Added myself to contributors table

[codecov-io]

Codecov Report

Merging #241 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #241   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           4      4           
  Lines         296    299    +3     
  Branches       71     72    +1     
=====================================
+ Hits          296    299    +3

Impacted Files	Coverage Δ
src/downshift.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b04cc25...e199cf6. Read the comment docs.

[kentcdodds]

This looks perfect! Thank you very much!

[kentcdodds]

I'm going to go ahead and ask that we wait for another maintainer to review this as well 👌 thank you!

[kentcdodds]

Would you like to add yourself to the contributors table?

[kentcdodds]

You could add "test" to this too if you want. Just update the file and commit. It'll update the readme in a commit hook 👍

[kentcdodds]

Sorry, I'm not sure what happened with this PR! Do you mind resolving conflicts and I'll get it merged.

Easiest way to resolve all-contributors conflicts is to just fix the .all-contributorsrc by hand, then commit, the README will fix itself!

[kentcdodds]

Perfect!

[kentcdodds]

One day we'll have a bot so you wont have to worry about dealing with merge conflicts in the contributors table... 😅

[kentcdodds]

Thanks so much for your help here and in #252! I've added you as a collaborator on the project. Please make sure that you review the other/MAINTAINING.md and CONTRIBUTING.md files (specifically the bit about the commit messages and the git hooks) and familiarize yourself with the code of conduct (we're using the contributor covenant). You might also want to watch the repo to be notified when someone files an issue/PR. Please continue to make PRs as you feel the need (you can make your branches directly on the repo rather than your fork if you want). Thanks! And welcome to the team :)