🚀 Feature request

Current Behavior

The type ErrorMessage doesn't have an id property.

Desired Behavior

It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.

Suggested Solution

Add id={this.props.id} to the outer component in ErrorMessage.

Who does this impact? Who is this

Describe the bug
The following PR introduced some breaking change in typings: https://github.com/beautifulinteractions/beautiful-react-hooks/pull/156/files#diff-b52768974e6bc0faccb7d4b75b162c99R19

Argument of type '() => void' is not assignable to parameter of type 'any[]'.
  Type '() => void' is missing the following properties from type 'any[]': pop, push, concat, join, and 27 more

There is an existing PR created to add docs to testing-library-docs from when testHook was part of react-testing-library. Since it was removed and the code merged with this library, the PR has stalled waiting on updates to change it to reference this library instead.

If anyone wants to take over the PR and update it accordingly, you are more than welcome. You can even [add yourself as a

It's important, I think, if the goal is to communicate that this can replace React in more ways than function.

Description

Graphql clients comparison (apollo client vs graphql-hooks vs urql).

Suggested implementation

List describing the advantages / disadvantages to other major clients. This library looks interesting but I don't see any advantage other file size.

why did you skip the onTap callback in version 5? Is there an easy way to create the onTap functionality, when dragging didn't take place?