Add logging functionality for command requests #2550
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lay command Signed-off-by: worksofliam <mrliamallan@live.co.uk>
worksofliam
temporarily deployed
to
testing_environment
GitHub Actions
Inactive
|
👋 A new build is available for this PR based on 656760c. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'd really like a world where it's easy for us to visualise user issues. Right now, we have to ask the user to paste the output channel and we spend a lot of time navigating that.
Ideally, we'd take the output from the output channel and we'd visualise it nicely.
I had some ideas for visualisations, for example:
I did a POC with just putting the data into a webview, but didn't commit this: