Namespaced components don't appear

[kendagriff]

When I namespace my components, the devtools can't find them. Furthermore, they appear to have meaningless data-reactids (".0.0.0.0"). Example:

Game.Views.Page = React.createClass({
  render: function() {
    return (
      <section className="page">Hello, World</section>
    );
  }
});

I reference my component using Game.Views.Page(). Is JSX responsible for producing meaningful information for the devtools? Is there no way to reference namespaced components using JSX?

[sophiebits]

Are you using jsx from React 0.9? It should set the displayName property appropriately.

[kendagriff]

I'm using JSX for mimicking HTML, but as I understand it, JSX cannot take nested object names for components, right?

[sophiebits]

The JSX compiler transforms your original code into

Game.Views.Page = React.createClass({displayName: 'Page',
  render: function() {
    return (
      React.DOM.section( {className:"page"}, "Hello, World")
    );
  }
});

The displayName property allows the dev tools to show the right component name.

[sophiebits]

There's currently no way to use a namespaced component from JSX without bringing it into local scope though. See facebook/react#760 for some discussion on this.

[kendagriff]

Thanks, Ben. I hope they introduce that.

Yes, it's adding the displayName property, however, the React tab in Chrome
DevTools is still as empty as can be. Am I missing something obvious?

On Thu, Mar 6, 2014 at 12:18 PM, Ben Alpert notifications@github.comwrote:

There's currently no way to use a namespaced component from JSX without
bringing it into local scope though. See facebook/react#760https://github.com/facebook/react/pull/760for some discussion on this.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-36925395
.

Kendall
Co-Founder, Banzai
kendall@teachbanzai.com | 435.503.1462

[sophiebits]

See https://github.com/facebook/react-devtools#the-react-tab-is-blank -- does that solve your problem?

[jaredly]

Is this still an issue?

[kassens]

Please open a new issue if this is still a problem. We've since launched a new version of the devtools on the Chrome store (it should've auto-updated already).