docs(flow.trace): correct flow trace search visualization #399
Conversation
This file contains hidden or 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
stijnmoreels
added
bug
✅ Deploy Preview for invictus-for-azure ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
GoutsmitSam
approved these changes
Jul 3, 2025
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.
The feature documentation page explaining the flow trace capabilities was incomplete on some parts (now showing/explaining DSAV, for example) and too detailed on others (deep-dive into regular expressions).
This PR tries with
.gifimages to unburden the text and with Markdown tables to more easily explain the possibilities for the flow trace search.Closes #397