Comments (3)
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.
Related Issues (20)
- As an app developer, I want to use an abort handler wrap
- IPFS deploy module doesn't work w/ Node v18
- CLI version 0.10.4 and 0.10.5 produce `wasm-bindgen` TypeScript artifacts when building Rust Wasm wrap HOT 1
- `polywrap.docs.yaml` Doesn't Work For Interfaces HOT 1
- `polywrap deploy`'s IPFS module fails with node version 18 HOT 1
- HTTP deployment does not work if no headers are specified in the deployment config
- Remove ENS deployer from CLI
- Use `npx degit` Instead Of `polywrap create`
- IPFS Deployer possibly duplicates subdirectory paths when deploying HOT 1
- `polywrap build` command's default manifest is using an old manifest version
- Enable polywrap CLI to be installed via curl using vercel/pkg compiler
- Bug: We should make sure multiple rust-wraps work within a workspace HOT 1
- Update rust app template to use rust-based tests (w/ Rust client) HOT 1
- Polywrap Manifest: Make use of defaults
- `npx polywrap deploy` fails with MODULE_NOT_FOUND for `@polywrap/core-js`
- Polywrap Manifest: Improve imports HOT 1
- TS wraps don't build due to missing pwr cli
- golang wrap not building due to invalid wasi import
- Go Wasm bindings are missing an abstract class for Module HOT 1
- Go wraps cannot throw errors
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wrap-cli.