docs: update quickstart to include messy output example #851
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
|
Taken with firefox from local dev build. |
|
Updated the link as I realised that this is ReStructured Text not Markdown |
yottahmd
approved these changes
Feb 20, 2025
|
😊 Thank you @yohamta , I don't know about amazing, just hoping to help where I can. |
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.
See: #841 (comment)
This I hope is a tiny edit, which would have answered some questions I had about output.
I might ask if this is successful to also add some docs to the output command, documenting some alternative patterns.
This is the kind of thing I encounter at work all the time. Some third party component that has noise in it's output, but maybe isn't OpenSource or is retrieving data from somewhere that means I need to make a tool to clean the data.