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
Yeah, a valid point, sometimes you don't need an id, so you shouldn't be forced to define it.
For now, you need to provide id always, as it is a pretty important factor of framework mechanisms, and as you notice we don't generate any random one when it doesn't exist.
Also maybe you want to share some kind of example so we could understand better what you would like to achieve.
Or is it only about not being forced to create an id when you don't need it later?
For now, I will mark it as enhancement and hope someone picks it up in the near future.
If an ID or no ID specified is not specified for each node element, at some point the app will crash.
The text was updated successfully, but these errors were encountered: