hooks

🚀 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

After upgrading to v4 (and going through the migration guide) we get this warning (from webpack-dev-server):

"Compiled with problems:

WARNING in shared module react

No required version specified and unable to automatically determine one. Unable to find required version for "react" in description file (/path/to/project/node_modules/@tanstack/react-query-devtools/packa

https://github.com/sequelize/sequelize/blob/8a1429d6044123bba3a3f312b2e0c74b0c829990/lib/model.js#L1271

If I create any model with
charset: 'utf8mb4', collate: 'utf8mb4_general_ci'

sequelize translates it to this for mysql

CREATE TABLE IF NOT EXISTS tablename ... ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8mb4_general_ci;

On stepping through the code, it seems that the issu

The current code coverage is around 84%, it would be nice to have a 100% score and I'd love to have some help in doing so. Please feel free to open any PR.

I'm trying to automate the interaction with WindowsTerminal. It seems to be a UWP application, which I have no idea how to start such application directly using Application().start. I've tried to locate it using Desktop, but got quite confused..

Any help on this?

Use this template instead https://codesandbox.io/s/r3f-template-jrl1f

Is your feature request related to a problem? Please describe.
Some users require saving objects like ES6 maps which can't be JSON.stringified without a replacer function.

Describe the solution you'd like

We need replacer/ reviver functions optionally to be sent as arguments.

useLocalstorageState('key', value, {
  replacer: () => {},
  reviver: () => {} 
})

`

Describe the bug
The sidebar has overflow: scroll causing scrollbars always to be visible on Windows

To Reproduce
Steps to reproduce the behavior:

1. Go to documentation using Windows

Expected behavior
There should not be scrollbars before the content overflows

Screenshots
![image](https://user-images.githubusercontent.com/2255960/99193174-891e7c00-2777-11eb-8ceb-79