Dustan Kasten
Dustan Kasten
I don’t think it does... this is the result of console.logging ``` docgen.parse(fs.readFileSync('./my-component.js')) ``` ``` { description: '@private', props: { to: { type: [Object], required: true, description: '' }, name:...
Hmm.. so I have stateless components not getting a `displayName` as well as ``` import React, {PropTypes, Component} from 'react'; class Tabs extends Component { .... } export default Tabs;...
:+1: ...does babel still follow that approach for displayName handling?
I vote @mik01aj for those one :)
@syranide thanks for your response. I’ve been thinking on this for a few days (and will be for a while). I definitely get your concern. My ambition may be that...
I currently have a script started to sync everything from `examples` to documentation pages as well ;)
I _think_ that the streaming server Sebastian referred to is the new React Flight work in https://github.com/facebook/react/tree/master/packages/react-flight-dom-webpack.
Hey @abritinthebay, thanks for checking out the project and asking the question! I do not know enough to answer that well. It seems Firmata is the standard protocol to control...
Yeah, I think that would be feasible. Right now the internal API is definitely dependent on the Firmata API. I believe Johnny-five has the ability to interop with non-firmata boards...
I want to handle rendering to multiple boards at once. See #10. I also added a commit that supports wrapping johnny-five components and rendering to a johnny-five board yesterday (cc2677f2d95f614693e534efca2a8507c43f5198)...