Need support in writing a preview plugin that supports decode and preview JWT files.

[smangels]

What system are you running Yazi on?

Linux X11

What terminal are you running Yazi in?

kitty 0.38.1 and ghostty 1.0.0 build 8469

yazi --debug output

Yazi
    Version: 0.4.2 (Homebrew 2024-12-20)
    Debug  : false
    Triple : aarch64-apple-darwin (macos-aarch64)
    Rustc  : 1.83.0 (90b35a62 2024-11-26)

Ya
    Version: 0.4.2 (Homebrew 2024-12-20)

Emulator
    Brand.from_env      : Some(Ghostty)
    Emulator.detect     : Emulator { kind: Left(Ghostty), light: false, cell_size: Some((20, 41)) }
    Emulator.detect_full: Ok(Emulator { kind: Left(Ghostty), light: false, cell_size: Some((20, 41)) })

Adapter
    Adapter.matches: Kgp

Desktop
    XDG_SESSION_TYPE           : None
    WAYLAND_DISPLAY            : None
    DISPLAY                    : None
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

NVIM
    NVIM          : false
    Neovim version: 0.10.3

Variables
    SHELL           : Some("/bin/zsh")
    EDITOR          : Some("nvim")
    VISUAL          : None
    YAZI_FILE_ONE   : None
    YAZI_CONFIG_HOME: None
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: Some("\n    --color=fg:#d0d0d0,fg+:#d0d0d0,bg:-1,bg+:#262626\n    --color=hl:#5f87af,hl+:#5fd7ff,info:#afaf87,marker:#87ff00\n    --color=prompt:#d7005f,spinner:#af5fff,pointer:#af5fff,header:#87afaf\n    --color=border:#7aa2f7,label:#aeaeae,query:#d9d9d9\n    --height 60% --extended --border")

Text Opener
    default     : Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block-create: Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block-rename: Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })

Multiplexers
    TMUX               : 0
    tmux version       : tmux 3.5a
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : 0.41.2

Dependencies
    file          : 5.41
    ueberzugpp    : No such file or directory (os error 2)
    ffmpeg/ffprobe: No such file or directory (os error 2) / No such file or directory (os error 2)
    pdftoppm      : No such file or directory (os error 2)
    magick        : No such file or directory (os error 2)
    fzf           : 0.57.0
    fd/fdfind     : 10.2.0 / No such file or directory (os error 2)
    rg            : 14.1.1
    chafa         : No such file or directory (os error 2)
    zoxide        : 0.9.6
    7z/7zz        : 17.05 / No such file or directory (os error 2)
    jq            : 1.7.1

Clipboard
    wl-copy/paste: No such file or directory (os error 2) / No such file or directory (os error 2)
    xclip        : No such file or directory (os error 2)
    xsel         : No such file or directory (os error 2)

Describe the question

Hi,
I'm reaching out for people willing to support me in writing a native previewer plugin for JWT files. Nats server and account configuration is stored in such a format and when navigating through hundreds of JWT files in a file structure for a cluster, it would be nice to have native preview support in Yazi (with code highlighting of the resulting JSON content inside the payload).
Many thanks in advance.

Anything else?

No response

Checklist

• I have searched the existing discussions/issues

[AnirudhG07]

Hi! @smangels Mostly any yazi "previewers" are based on "cli" tools that show (only) the preview for it in the terminal. Many JWT CLI's I have seen also allow editing and other functionalities, than just a good preview.
If you know of something of a JWT previewer, I can make it for you.
Or
If you are developing a new tool itself, I would like to help out(if possible).

[smangels]

Hi, I've managed to get it up an running decoding the JWT through a CLI tool and are happy to share the code with you. It would be even better if we could get it decode natively in Lua. But I've struggled to get a development environment up and running. Did you manage Anirudh? /Sebastian BR, Re:

…

Hi! @smangels <https://github.com/smangels> Mostly any yazi "previewers" are based on "cli" tools that show (only) the preview for it in the terminal. May JWT CLI I have soon also allow edits and other functionalities than just a good preview. If you know of something, I can make it for you. Or If you are developing a new tool itself, I would like to help out(if possible). — Reply to this email directly, view it on GitHub <#2109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABC3BOXYNB4IH5VERLXIBVT2KCTSJAVCNFSM6AAAAABUJRJQK2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBQGQ3DEMY>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[AnirudhG07]

We need not convert it to a Lua code, if the CLI can be installed, and can just preview nicely, then it should be enough in that language itself.
Can you share the repo? And a screenshot of the preview of how it looks?

[smangels]

The repository can be found at https://github.com/smangels/jwt.yazi and it contains a test.jwt file. The issue is that we are using our own JWT decoder binary and my gut feeling tells me that it would be much cleaner to simply implement the decoder feature in plain Lua instead of relying on an external tool - shouldn't be too complicated. https://gist.github.com/inaiat/02bf5d11732d8e4d7b7546399a3a49af What do you think? Re:

…

We need not convert it to a Lua code, if the CLI can be installed, and can just preview nicely, then it should be enough in that language itself. Can you share the repo? And a screenshot of the preview of how it looks? — Reply to this email directly, view it on GitHub <#2109 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABC3BOQXNRB3MUJHQQXU7GD2KE5AHAVCNFSM6AAAAABUJRJQK2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBQG4YTGOI>. You are receiving this because you were mentioned.Message ID: ***@***.***>