-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Implicit property type change from string to object from 1.5.0 to 1.6.0 #5541
Comments
I think is unintended. In any case, I think it was |
This was indeed undefined behaviour prior to 1.6.0. Though even in 1.5.0 it doesn't do what you think it does. No schema and an empty schema ( There are a couple of reasons this change was made:
In short, the 'new' behaviour is intended. While we could consider changing the semantics of no given schema, I'm not fond of the idea that no-schema and |
no schema and schema : {} are both undefined to me should probably |
Description:
Before 1.6 I could do
but now in 1.6 I must do
In 1.5 the output of e.g
componentname="test"
would be"test"
but now it is{}
unless the string type is forced via the schema.Example https://glitch.com/edit/#!/aframe-16-implicit-component-type with output in the console.
This is not particularly a problem but it lead to unexpected behaviors for me. I briefly checked the change log and couldn't find it as a change. Is this expected? Documented?
The text was updated successfully, but these errors were encountered: