Configurable Core Logging about wrap-cli HOT 3 CLOSED

Logging will be used (in the future) to verify call stacks of various client implementations. In order to do this, we'll need a common log format that each client will be capable of emitting (using a wrapping process of course).

Ideally, when using the client (in JS for example), you could decide as the user how you want messages to be logged using the client's config options. This way you can choose to do console logging, or send logs remotely to a logging server such as a graylog server. This would be useful for aggregating various different client logs into a single logging server, which can then check for differences in output. See here for more info: https://www.npmjs.com/package/gelf-pro

from wrap-cli.

Questions we'd want to be able to answer with this logging:

• Where are APIs being resolved from? For example: if you're using the CLI, and provide a custom IPFS provider when running the build command, you should be able to read the logs to see if your schema dependencies are being pulled from that location.

from wrap-cli.

Moving this issue here: #187

from wrap-cli.