Centralise logging
Summary: Centralise connectivity logging into a single place. By having all logs go through a single interface, then it becomes trivial to manipulate them as needed. In this change, this is not done. In subsequent diffs, logs will be dispatched via an event and will be visualised in the Connectivity Hub. Reviewed By: passy Differential Revision: D47185054 fbshipit-source-id: fb5eab98895be0c8f61fb9a77d3e66d6a8dbcb27
This commit is contained in:
committed by
Facebook GitHub Bot
parent
49d1a8b0fa
commit
fc38355eee
@@ -12,7 +12,12 @@ import {FlipperServerImpl} from '../FlipperServerImpl';
|
||||
import {ServerDevice} from './ServerDevice';
|
||||
|
||||
/**
|
||||
* Use this device when you do not have the actual uuid of the device. For example, it is currently used in the case when, we do certificate exchange through WWW mode. In this mode we do not know the device id of the app and we generate a fake one.
|
||||
* Use this device when you do not have the actual uuid of the device.
|
||||
* For example, it is currently used in the case when, we do certificate
|
||||
* exchange through WWW mode.
|
||||
*
|
||||
* In this mode we do not know the device id of the app and we
|
||||
* generate a fake one.
|
||||
*/
|
||||
export default class DummyDevice extends ServerDevice {
|
||||
constructor(
|
||||
|
||||
Reference in New Issue
Block a user