Fabien Mauquié
Fabien Mauquié
Hi! Thanks :) This one is not easy... There are multiple ways it could be solved, and they all have issues. These are the ones I've thought about: - Patching...
@Kepro I'll do this ASAP, I just need to add a little thingy to help @mathieumg :) @mathieumg are you using ReactDOM.render() directly in a directive linking function then ?...
I just pushed (and released to NPM @Kepro :) ) version 0.3.0 that should fix this issue. It ships with automatic handling for `ngReact` users, a HOC for manual React...
Right, and right... Published v0.3.1 to patch these.
@Kepro I need more information in order to help you: are you using `ngReact`? Are you loading it before `react-angular` ? If you are not using `ngReact`, you need to...
I think you're loading ngReact after react-angular in the loading order in your app. You can try to change this (make sure your files are loaded in the correct order,...
I'll add a warning in development mode if I can detect an inconsistency in the module loading order (when I get time 😄)
The idea is that you should be able to use your Angular code as if there was no React in between. In particular, if you're in a route manages by...
I released a new version that is not subject to loading order. @Kepro can you try? You need to add a module dependency to your Angular app, It is explained...
@mathieumg you should try using the HOC, it will work better with a custom ReactDOM call. The scope should not be different, at least not from what I read in...