add missing 'suppressRefError' option typings

[rifler]

What:
Missing TypeScript (TS) typings added - second argument to getRootProps and getMenuProps functions

Checklist:

• Documentation
• Tests N/A
• Ready to be merged
  
• Added myself to contributors table
  

[kentcdodds]

Changes look great except those in the README. Could you remove that? Thanks!

[kentcdodds]

This is excluded from the docs intentionally. It's a pretty far edge case so I don't think it's worth including in the docs.

[rifler]

fixes done
I just noticed that there is very similar PR - #534
They overlap a bit

[kentcdodds]

Thanks! @rifler, could you review #534? Then I can merge it and you can update this one to fill in any gaps?

[rifler]

@kentcdodds LGTM, I'll rebase my PR after merging #534

[rifler]

done
Do you run prettier/linters on precommit? It's a bit hard to manage semicolons manually

[kentcdodds]

Yes... Do you have dependencies installed?

[rifler]

haha, it was so obvious, sorry. I had an experience to run prettier/linters (without --fix) also on CI, I think it is more reliable solution than pre-commit

[kentcdodds]

I'm not sure why the precommit script is not running for you. It should be automatically generating the contributors table in the README as well as running prettier on all changed files... 🤔

[rifler]

It's because I didn't install npm deps, as you mentioned earlier. It was obvious, but I didn't catch it :) Now it is ok.
About CI I meant the following - CI checks are more reliable, e.g. if someone (like me) forget to install deps (or use --no-verify), than CI fails
For example my PR contains style fixes (semi removal) from previous contributor
https://github.com/paypal/downshift/pull/556/files#diff-494415c3af35245ecae73f5d42d8b331R117
I suppose it is because he forgets to install deps too.
Also we could avoid errors like this - 5acaf86

[kentcdodds]

How do you suggest we update the pull request someone else opened? I know it's possible, but it'd be a bit more work than I would like to do myself.

[kentcdodds]

🎉 This PR is included in version 2.1.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[rifler]

On CI we don't modify code, just fail check. After that author and reviewer realise that something went wrong with precommit hook and fix it

Summarize:

1. Pre-commit: we use lint-staged, lint and fix only changed files;
2. CI on pr change: lint all files (not fix!), fail check on error.

We ran into same problems with linters, because colleagues forget to install deps or pass --no-verify to git or other reasons.

Nevertheless, thanks for your quick reaction for this PR!

[kentcdodds]

Oh, we definitely do that via the validate script. I'm not sure why that last one got through. I probably merged it before the build was finished or ignored the failing build because we'd been having intermittent build failures anyway. Either way, it was my fault 😅