Great work!
You could direct the local replica session runtime stdout and stderr to a file, that is then used to display it in a view to the user. This could be along side commands not specifically related to existing views, such as starting/stoping the local replica; or an interactive inline shell view for the curious user.
May be a bit early, but extensibility is key feature of this entire space so whatever’s needed for programmable plugins (that could provide for a Mops/CanisterGeek/Cyclops/SNS/etc integration) that could added as additional entries on the left panel. A point of departure for this kind of thing might be a “hello world” example of integrating an inline CandidUI view (or another option might be possible with the running Motoko in the browser package that exists).
How about a view devoted to testing (if implemented in the code base, could even generate the suite using the Vyber? iirc library) showing coverage and other related stats with possible features like creating/exporting/importing snapshots. Testing is really so amenable to automation and would fit right in along the rest of this app’s purpose and flow.
.did viewer/editor/translator to cli/or other language bindings?
Once again, really great work!
