Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core:schema:warn about component/system 'undefined' when using <a-primitives> #40

Closed
Zacqary opened this issue Oct 20, 2016 · 3 comments · Fixed by #41
Closed

core:schema:warn about component/system 'undefined' when using <a-primitives> #40

Zacqary opened this issue Oct 20, 2016 · 3 comments · Fixed by #41

Comments

@Zacqary
Copy link

Zacqary commented Oct 20, 2016

I get that the gist of aframe-react is that we're not supposed to be using stuff like <a-sphere> in lieu of always using the <Entity> component. But being able to call <a-sphere> A) saves a lot of typing, and B) seems to work.

I figured the problem would be that React has patchy support for custom attributes, but as it turns out:

<Scene embedded>
   <a-sphere position="0 0 -15" color="red" radius="1"/>
</Scene>

renders perfectly fine. The only problem I get are these warning in the console:

core:schema:warn Unknown property `color` for component/system `undefined`. +2ms
core:schema:warn Unknown property `radius` for component/system `undefined`. +3ms

I don't think I've run into any other issues besides that, so far. But what are these warnings about? They don't show up when I build my spheres with <Entity>

@ngokevin
Copy link
Collaborator

It's not against using <a-sphere>, it's just that aframe-react doesn't have to do anything special in that case, and React Components can sort of replicate the creation of such pre-fabbed entities.

The warnings are probably just a bug with the A-Frame primitives. It's near the top on my list of stuff to polish, but my list is pretty long...

@ngokevin
Copy link
Collaborator

might have been fixed

@natesena
Copy link

Still getting the issue when I create my own component

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants