-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stream Inspector #17
Comments
Inspector will be nice, but I will raise you a REPL for this, it will be magnificent. |
@lyuboxa what would a repl look like? Would you have to create a "conduit cli" to make this possible? |
I think any tooling that can be used to inspect data real time and does not involve explicit parsing will be useful. When @hariso and I were discussing this something like this came to mind:
I think an interactive REPL will be useful, a console or whatever you want to call it. |
@lyuboxa A REPL doesn't sound very composable to me 😕 Why not rather provide a simple CLI command to get the records? This would let you compose it with other tools like
Sidenote: I think it's a bit off-topic to talk about a CLI/REPL in this issue, it sounds like a whole separate feature by itself. |
Does it have to be? REPL are interactive tools for evaluation, not unix commands. Both options have their merits.
Yup for sure. |
Here's a separate issue for that: #697. |
All the tasks are done, closing the issue. |
The goal is to give folks the ability to see what's happening inside the stream. This is not like
tail
. This is more likepeek
. Pull out some information from the stream so that a developer can see the data and data types.The text was updated successfully, but these errors were encountered: