Selene warning: Property table mixes two data structures

[wireofparadise]

The property table mixes an array with a dictionary, which results in the following selene warning:

mixed tables should be avoided, as they can cause confusing and hard to debug issues such as during iteration or encoding
note: help: change this table to either an array or dictionary
selene::mixed_table

This is not necessarily an issue, but the question arises: why not just accept children as a special property like react or fusion?

[centau]

It seemed simpler and intuitive to make use of the language's feature of mixed tables to pass both properties and children.

I agree mixed tables should be avoided for logic and data, but I haven't come across issues with using them to declaratively pass properties.