You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whereas it should be within an entity description (see example below).
Also, no error is raised when we define an entity field in the YAML that does not exist in the class datastructure. This is error prone (e.g. one could set friction there, as in the second yaml below, but currently it just ignores it and set the default value instead).
To check if there are similar issues for other parameters.
Whereas it should be within an entity description (see example below).
Also, no error is raised when we define an entity field in the YAML that does not exist in the class datastructure. This is error prone (e.g. one could set friction there, as in the second yaml below, but currently it just ignores it and set the default value instead).
To check if there are similar issues for other parameters.
To define friction in the YAML currently we do:
Whereas we should do (if e.g. we want to have different friction in different entity subtypes):
The text was updated successfully, but these errors were encountered: