feat(inspect): add sixel render support#888
Open
bergzand wants to merge 1 commit intokaspar030:mainfrom
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
With #807 a subcommand to print the tree of builders was added. While that PR added a way to print the builders with a tree-like text shape, it can obviously be improved upon.
This PR adds support to print the builders as a tree graph in a terminal. This way users can get more insight in how builders relate to and depend on each other.
The output requires Sixel support in the terminal application (see https://www.arewesixelyet.com/). Rendering uses mermaid format with mermaid_rs_renderer for pure-rust mermaid format parsing.
Testing
Run the following in a laze project
Make sure the terminal emulator supports Sixel.
Example output