🚀 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

Documentation Feedback

How can I test the messaging().onMessage method?

I tried to issue the SharedEventEmitter.emit ('messaging_message_received') event but was unsuccessful.

Any workaround?

Consider this scenario:

My phone is connected to WiFi(4g), the power goes off, and my mobile data(2g) kicks into action. If there were multiple assets fetched for 4g, all their low quality equivalents will now be fetched.
This will also happen when I am travelling between places as my data speed keeps fluctuating.

I am not sure what the solution to this problem is but I believe we shouldn'

Can we build an advanced app with data fetching and similar things in easy peasy docs??

Like how redux has, but may not be the same

Problem

1. I am unable to drag a note from trash to all notes. I feels like this should be allowed.
2. Also I think it's a little strange that 'All notes' doesn't actually mean 'all' (does not contain trashed notes and scratchpad).

Solution

1. Enable a note to be restored from trash by dragging it into 'All notes'
2. Perhaps 'All notes' should be renamed to 'Notes'?

Notes
I'

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

The ReactFire repo now uses the All Contributors spec to recognize the contributions of everyone that has helped out with ReactFire v2.

In your own example: https://codesandbox.io/s/react-form-custom-select-multi-select-inputs-6962t

The canSubmit is true even before the two colors in the multiselect have been set. As long as the single select have been set, it's all good.

Is this expected?

Intended outcome

I'm building an application, and after doing some work with MobX, I ran a production build to ensure everything was working as expected, but it errored out. Development build does work exactly as intended, however.

Actual outcome

I get the following error:

✖ ERROR ./node_modules/mobx-react-lite/dist/observer.d.ts
ERROR in ./node_modules/mobx-react-lite/dist

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

Package

graphql-hooks

Environment

• graphql-hooks version: 4.3.0
• react version: 16.12.0
• Browser: Chrome

Description

I noticed the data variable returned from useQuery is undefined when first rendering a component. This collides with the fact that the types say it's always defined.

See index.d.ts:

interface UseClientRequestResult<ResponseDat

For Firestore collections and docs, it would be nice if each of the ...Data hooks would automatically add the idField (if provided) as a key/value to the <T> generic.

For example, the useDocumentData hook would return something like T & { idField: string } instead of just T. In this case, idField should be represented by the actual string value entered into options.idField.

D

The problem

Add @kevinwolf/eslint-config for linting

The solution

Remove all eslint related packages and install @kevinwolf/eslint-config as a devDependency (also update eslint config).

Notes

Make sure all test passes and i

https://github.com/facebook/react/issues/18178

my strack trace links the above issue with this code in react-use-form-state:

if (formState.current.touched[name] == null) {
 >>>  formState.setTouched(_defineProperty({}, name, false));
}

I'm still digging into this because Cannot update a component from inside the function body of a different component. has popped u

We started this project not quite long after Next.js became public and we haven't really touched the README 😅

We've just been improving the code section and making it a lot better. I guess it's time to give the README a new structure, basically to pass the right message to new users.

Let's do this! 🚀

Redux Style Guide: https://redux.js.org/style-guide/style-guide

• Do Not Mutate State: Yes
• Reducers Must Not Have Side Effects: Yes
• Do Not Put Non-Serializable Values in State or Actions: Yes, but not necessarily
• Only One Redux Store Per App: Yes but not necessarily
• Use Redux Toolkit for Writing Redux Logic: No
• Use Immer for Writing Immutable Updates: Yes, but not necessarily