We can add a quick toggle on tab handle to quickly switch a widget to full area and back to normal.

This is more likely an MochiFrontEnd enhancement

Watch query variable takes a query as a value and watches the query changes if there is any query depending on them.

Connection manager currently drops the connection definitions, integrate with StateDB.

How to separate cards in markdown for import?

For importing from .md, you mention to use --- in the markdown to separate sides of cards …

but you don't mention how to separate cards themselves. How do we do this?

(Maybe I missed it?)

please reply, and update your docs to explain this to new users. :)

User will be able to pass a query editor model when activating the widget.

Widget will be able to notify the user about the changes made/commands run

User should be able to create query variables. Much similar to postman

We must implement a heartbeat to the connector interface. We will use this interface on connector manager to poll all connections to detect disconnect state. If a connection is disconnected we should give user a feedback.

Query errors received from the connector should be shown to user.

Best way to that may be to create generic connector errors and throw them in the connector code instead of plain errors.

we can catch these errors in the extension level and handle accordingly.

Provider a shell for editing queries for different query backends

We want to add a history widget to the left area.
This widget will keep track of the history and save it to the mochi service.

We can implement this widget in the query editor extension.

Whenever a new table viewer is activated user will also pass a viewer modal. User will be able to manipulate the viewer view using the modal and modal will be able to notify the user about changes made to viewer view.

Required items

• Limit setting
• Current page arrows
• Refresh button

User should be able to save queries to be able to re-use later

Query results should be editable.

Main challenge is to come up with a unified way to handle commits.

Best way to handle this could be to give connector author a way to get notified when a cell is edited.

Author can collect the updates until it they are committed and save when it is updated.

But this way would create a confusing dataconnector interface.

Maybe instead we can create another interface to wrap query result edits. With each edit we can ask connector author to update the wrap. and wrap interface can have a build method to generate a
publishable query.