-
-
Notifications
You must be signed in to change notification settings - Fork 348
Conversation
Uses the convention for HOC display names as outlined in the React documentation. Closes #466
… (if it needs to be brought back alive use error boundaries)
Besides processing a lot of TODO's, the biggest open question atm is how to integrate with the DevTools. |
Co-Authored-By: mweststrate <mweststrate@gmail.com>
mobx-react@6.0.0-rc.2 is now available! |
Just a heads-up, it seems that it breaks when attempting to use https://codesandbox.io/s/j3k4p2jkv5 I did some digging, it seems |
The @mweststrate I don't think you should be providing a minified code as a |
Fixed in mobx-react@6.0.0-rc.4
…On Fri, Mar 22, 2019 at 8:37 AM Daniel K. ***@***.***> wrote:
The h is not the Observer, it should be React.createElement, but it's
indeed missing in there for some reason. The Observer is minified under y
and is there available.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#644 (comment)>,
or mute the thread
</~https://github.com/notifications/unsubscribe-auth/ABvGhLoom7uJ6zF9BiJjjbk0jojOwKb_ks5vZIhPgaJpZM4aztsd>
.
|
Are you using terser rather than uglify es? Terser fixed some react minification bugs |
No, jsx wasn't configured for microbundle, causing it to default to `h`
instead of `React.createElement`
…On Fri, Mar 22, 2019 at 10:44 AM Javier Gonzalez ***@***.***> wrote:
Are you using terser rather than uglify es? Terser fixed some react
minification bugs
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#644 (comment)>,
or mute the thread
</~https://github.com/notifications/unsubscribe-auth/ABvGhN7CTAE8nN_GBc0Rrf-3rhx7fmYiks5vZKX5gaJpZM4aztsd>
.
|
So I think you should remove reexport of |
src/index.js
Outdated
} | ||
__MOBX_DEVTOOLS_GLOBAL_HOOK__.injectMobxReact(mobxReact, mobx) | ||
} | ||
export { Provider } from "./Provider" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note here we should probably export the Context object as well so people can make a custom hook for it. It's to support an easier migration instead of expecting from them to rewrite to new Context in a big swoop.
export { Provider } from "./Provider" | |
export { Provider, MobXProviderContext } from "./Provider" |
README.md
Outdated
|
||
`mobx-react@6` and higher are no longer compatible with the mobx-react-devtools. | ||
That is, the MobX react devtools will no longer show render timings or dependency trees of the component. | ||
The reason is that the standard React devtools are no also capable of highlighting re-rendering components. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
devtools are no also capable
- what did you mean here? Looks like a typo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@macbem Use the suggestions next time please
The reason is that the standard React devtools are no also capable of highlighting re-rendering components. | |
The reason is that the standard React devtools are also capable of highlighting re-rendering components. |
See #640