WIP - Inspector component #316
Conversation
|
So if you want to try this out in more depth you could try doing some kind of a URL rewrite with parseDocumentLink/createDocumentLink when a user holds certain keys. |
|
@pvh after thinking a bit more about it, I'm thinking loading arbitrary document into Inspector view isn't the best option, as inspector needs to maintain it's own state e.g. which parts have being unfolded, additionally I wanted to add a field to type in jq expressions so only relevant data can be displayed. All this state needs to go somewhere and dumping it into document itself doesn't seem right. I'm considering to use For opening I'm thinking something like long option key should surface inspect button over cards to open new inspectors cards for those. |
- Inspector document at the moment just contains `targetURL` field of the document being inspected, but in the future it will be extended to store state like (un)folded substructures and possibly more. - At the moment view initially renders title editor to enter `targetURL` but ideally it would possibly have dropdown like omnibar to just choose document from the active board. I also would like to have long press on Option/Alt key to activate overlay over widgets with a button to launch an inspector for any of the widgets.
Draft of inspector widget (based on #311) that I would like to make into a built-in view for poking around arbitrary documents in the system. At the moment there is no good way to open a document you'd like to inspect other than copying the URI of the document and pasting it back with modified content type e.g.
Which should give you something like this
I also would like add a way to edit fields, but observablehq does not support modifications & I'm not in the mood of rewriting it.
Alternative might be to provide little console like input for JS repl kind of execution but that probably should be a separate widget.