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
I know that this is a difficult task, so I am posting my idea here and not in issues, but I think it would be very useful thing.
Please look at the screenshot:
On the left you see a table that represents the structural description of the user interface. On the right you see the result. The principle is somewhat similar to HTML. So, the type of each nested table is specified in its "node" key. I don't get any hints filling out such tables, but I could if there could be some way to specify a rule for mapping types with table keys/values.
@sumneko Thank you! I am aware of the fact that it is achievable. I did before exactly as you showed in your example, but I'm not comfortable creating new variables for each table item when this table is deeply nested. I just want to declare single table and return it. So I had to abandon the handy hints in favor of code simplicity.
Yeah, that's cool! All the nodes in my table inherit from the drawable class, so I can get general hints this way, but still I don't get more precise hints for subclasses, such as drawable.text, drawable.window, etc.
Currently you can combine all fields in one big class.
But I think what you want is to automatically identify the current subclass based on the node field, which requires future implementations to type narrow based on the field.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I know that this is a difficult task, so I am posting my idea here and not in issues, but I think it would be very useful thing.
Please look at the screenshot:
On the left you see a table that represents the structural description of the user interface. On the right you see the result. The principle is somewhat similar to HTML. So, the type of each nested table is specified in its "node" key. I don't get any hints filling out such tables, but I could if there could be some way to specify a rule for mapping types with table keys/values.
All reactions