dprint VS vaultrs

Prettier is opinionated. dprint is highly configurable.

I mean, I know I am a bad person because of those long names, but that is how life goes sometimes! And the blank line there at the top is just very important to like, catch one's breath, while reading this code.

(I'm really just posting this in the hopes that somebody will throw me a "Bro, just use hpstrlnt, it totally lets you configure that!" -- I have not actually tried Rome to see if it does (it's Monday morning and I'm not quite ready to be disappointed again...))

[1]: dprint is good, and I recommend it as the best code formatter I currently know of: https://dprint.dev/

If it's something in the vein of one of those things then, worst case, you generate the code first, then run it through something like dprint.

Why not compare Rome formatter to the actual competition, https://dprint.dev/ ?

I wouldn't really trust a "one to rule them all" tool. As you said, though, I do think there is a practical use to not having a markdown, yaml, and JSON formatter all as separate tools. Maybe even through in HCL as an added bonus.

I've already built something with Rust (https://github.com/jmgilman/vaultrs). I suppose I'll add it to my never-ending list of projects if I can't find something :)

Thanks! It was out of necessity - both Vault and Consul have really poor crate representation. The plan is to eventually get this and vaultrs to implement the whole API.

Just recently released a pretty decent overhaul of rustify that increases its ability to scaffold various HTTP APIs. It's nearing a 1.0 release as I don't see the feature-set needing to grow any past this point. It's been powering vaultrs for a while now and has really streamlined the process of scaffolding dozens of endpoints (probably close to a 100 in that crate alone).

I've written an extensive guide for how the crate is structured and how to easily get started with contributing. This is a great project for beginners to Rust as it's easy to extend but understanding it at a deeper level requires knowledge of core constructs. The guide is also a good read if you're interested in the design philosophy behind the crate and I'm happy to take any feedback to help improve it.