Support comment retention in fnox.toml (in fnox set)

[colelawrence]

I like to put all of my documentation directly into these TOML files so that other people can understand and read the like TOML files where things are defined to understand how they're linked. For now, my workaround is defining an fnox.README.md file.

[theutz]

I think this is a good point. It seems like fnox edit preserves comments, so if you're not worried about a colleague wiping your secrets out, that might also do as a workaround.

[colelawrence]

I can confirm that fnox edit preserves comments! That is working great.

[colelawrence]

I've added some comment preservation tests that are failing that can be observed in colelawrence@ff5d097 - I'd be happy to open as a PR

[nartamonov]

fnox set removes all comments, sadly.

[jaehong21]

Is there any further progress on this thread? I’m also interested in working on it.

[andrioid]

fnox import also wipes the comments. Usually this wouldn't matter, but I am missing a way to assign age-keys to developers.

I even tried doing like the ssh keys; adding an email after the key to signify the owner of it. That actually works fine for fnox get and fnox exec; but the import/setting stuff breaks with a bech32 hash error.

[CanRau]

Hmm for me it keeps all comments after fnox set, full line comments as well as end-of-line comments 🤷🏻‍♂️

I'm on macOS 26.3 using Ghostty 1.2.3 with zsh, maybe any of that matters 🤷🏻‍♂️

[jc00ke]

I'm seeing that fnox set formats the fnox.toml [secrets] into a single line if it was previously in a (recommended) table format:

[providers.keychain]
type = "keychain"

+[secrets]
+"SEKRIT_PASSWORD"= { provider = "keychain", value = "SEKRIT_PASSWORD", if_missing = "error" }
-[secrets."SEKRIT_PASSWORD"]
-provider = "keychain"
-value = "SEKRIT_PASSWORD"
-if_missing = "error"