I would like to make a feature request to make it easier for custom widgets to deal with tables: the ability to access certain Tulip APIs directly, without having to set up bot credentials. The way I would like to do this is to be able to pass in a Table, Query, or Aggregation reference as new input types when setting up a new custom widget. Imagine if you could do this:
What you would pass in wouldn’t actually be the table, it would be a reference to the table that is the table API, and has methods to get, create, update, delete. The get() would have to return some table metadata, at least to be able to map column names from field names – or even better, forget the field names and just let the keys in the resultset match the table field name rather than the ID.