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
This issue is a place to put all small changes that should be made to improve the usage experience, however, they are not currently the priority (but shouldn't be forgotten).
List:
Component IDs must be unique across all outputs (output_1 and output_2 can't define some_comp_id simultaneously). This is unnecessary, but with the current implementation, the user receives an error once they want to do it.
width, height, top, and bottom should be supported by more components. Users often need to warp components with view to achieve the desired layout.
Scene validation errors are not returned in response if the request is scheduled, they are logged instead.
Errors in complex scenes are hard to read, as there is no indication in which specific place they occur. If you get an error like: failed to deserialize ... it's hard to debug it in more complex scenes.
...
The text was updated successfully, but these errors were encountered:
This issue is a place to put all small changes that should be made to improve the usage experience, however, they are not currently the priority (but shouldn't be forgotten).
List:
output_1
andoutput_2
can't definesome_comp_id
simultaneously). This is unnecessary, but with the current implementation, the user receives an error once they want to do it.width
,height
,top
, andbottom
should be supported by more components. Users often need to warp components withview
to achieve the desired layout.failed to deserialize ...
it's hard to debug it in more complex scenes.The text was updated successfully, but these errors were encountered: