-
Notifications
You must be signed in to change notification settings - Fork 0
finish docs, cleanup, finalize #21
Comments
The hint about the Documentation will not only be visible at the GitHub site but also on the npm package information site. We should use a different phrase. <span class="laxar-developer-view">This is the developer version. Take a look at our <a href="http://www.laxarjs.org/docs/laxar-react-adapter">documentation site</a> with the released version.</span> And fix the link: |
Good points! |
I recommend the following text: <span class="laxar-developer-view">
Take a look at the <a href="http://www.laxarjs.org/docs/laxar-react-adapter-latest">documentation site</a> to browse documentation for all releases of this artifact.
</span> |
Cool thing, but I don't quite understand the meaning of |
@x1B Two more things:
|
Implemented on BREAKING CHANGEThe
For numerous examples, refer to the README.md. |
Short recipe on how to quickly adapt to the breaking change:
Before: function create( reactRender ) {
function render() {
reactRender(<em>Yo</em>);
};
setTimeout(render, 2000);
return {
onDomAvailable: () => render()
};
}; After: function create( reactRender ) {
function render() {
return <em>Yo</em>;
};
setTimeout(reactRender, 2000);
return render;
}; |
(Rebased onto feature/7-... branch)
Make sure that this adapter has everything required for LaxarJS v2:
The text was updated successfully, but these errors were encountered: