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 have run into this before, and it looks like this will play into several of the features we’ve been talking about — it is sometimes difficult to determine the type of an object (at least on the client), because of all the subclasses etc.
It would be nice if there was an easier way to at least determine the type (Instance, Function, Sharable, View, etc.) of an object immediately, without having to do sequential get()s of the parent schemas.
E.g.
in determining the editor to use
in tokenization, to determine if a function was selected and the next autocompletion should be filtered based on argument type
in conversion, limiting to certain schemas + subclasses, or minimally to instances
in typeaheads, filtering to a type rather than specific schema
maxbates
changed the title
sharables - "primitive" field (instance / function / schema / view)
sharables - "type" field (instance / function / schema / view)
May 27, 2014
Add a field on set() to add a field
primitive
which differentiates between the four major data typesshould also be in schema, e.g. function would encapsulate function, module, and subclasses of each
The text was updated successfully, but these errors were encountered: