this post was submitted on 06 Sep 2024
62 points (73.8% liked)
Programming
17351 readers
243 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think that's a user thing and it doesn't happen if you have a linter enforce 2 or 4.
That's part of the problem. Different number of whitespaces indicate different nesting levels and the YAML spec does not enforce them. These two horrible YAMLs are valid and are not equivalent:
So it's easy to enforce locally but you don't have to. And it's easy to see indentation on modern IDEs and you can even make your indents rainbows and collapse structures to make it easier to see what's going on, but I guess since some people want to write it in vi without ALE or a barebones text editor, it's bad? Like there are legit reasons it's bad, and other people have mentioned them throughout the thread, but this seems like a pretty easy thing to deal with. I work with ansible a bunch and YAML rarely is where my problem is.
Jesus, just what I want to do with the devops team - spend a few weeks standardizing on an editor and configuring them to edit yaml.
A few weeks? How do you stay employed? How do you even feed yourself at that pace? Blocked on making a sandwich, I've got the wrong type of bread.
It's three lines in an editor config file to standardize the indents across any editor: https://editorconfig.org/
In vscode, adding two extensions is all I need:, yamllint (if you don't use linters, I don't know how you do your job in any language) and rainbow indents. Atom had similar ones. I'm sure all IDEs are capable of these things. If you work at a place that forces you to use a specific editor and limits the way you can use it, that's not YAML's fault.
At a certain point, it's your deficiencies that make a language difficult, not the language's. Don't blame your hammer when you haven't heated the iron.
You know how many editor plugins I need to work with json? None.
You want an award? I hate working with JSON without a prettier.