Files
weave-scope/client
Tom Wilkie 9e61ad37f4 Get Pipes working again.
They stopped working because of the change to container node IDs (and rendered nodes IDs for containers).  The UI was comparing the IDs, which was never safe.  I have just removed that code.  This does leave the possibility of us having the pipe control operation take a long time, the user navigate to a different node, and then the terminal pop up, but I think thats better that teaching the UI to understand the format of the node IDs.
2016-01-19 16:47:48 +01:00
..
2016-01-19 16:47:48 +01:00
2015-12-16 13:45:37 +01:00
2015-11-11 18:42:48 +01:00
2015-05-20 10:45:35 +00:00
2015-12-10 12:52:44 +00:00
2015-05-19 10:02:02 +00:00
2015-10-26 17:49:21 +00:00
2015-12-10 12:52:44 +00:00
2016-01-19 16:47:05 +01:00
2015-08-24 12:41:17 +02:00

Scope UI

Getting Started

  • Setup: npm install
  • Build: npm run build, output will be in build/
  • Develop: npm start and then open http://localhost:4042/

To see a topology, ../app/app needs to be running, as well as a probe.

Coding

This directory has a .eslintrc, make sure your editor supports linter hints. To run a linter, you also run npm run lint.

Logging

The Scope UI uses debug for logging, e.g.,:

const debug = require('debug')('scope:app-store');
debug('Store log message');

To enable logging in the console, activate it via localStorage in the dev tools console:

localStorage["debug"] = "scope:*"