Stuff you configure in the UI is mostly stored in the database, not as YAML. Nearly everything you've configured using YAML is not editable from the UI. Whenever an integration moves from YAML to the UI (like the Proximity integration in a recent release), the YAML config is deprecated.

There's a few exceptions where YAML is stored in the DB (like if you have dashboard cards with custom configs) but YAML is going away over time as the UI gets more powerful, and is mostly just becoming a power-user thing.

[–] lone_faerie@lemmy.blahaj.zone 3 points 7 months ago (1 children)

That's true, I was thinking more about automations and scripts, which are still stored as YAML

[–] dan@upvote.au 3 points 7 months ago (1 children)

Oh yeah, good point. It might make sense for those to remain YAML to allow for more advanced tweaks. I learned programming in Excel 97 by recording macros and then viewing and tweaking the VBA code behind them, and this feels kinda similar (although YAML isn't a programming language).

[–] lone_faerie@lemmy.blahaj.zone 1 points 7 months ago (1 children)

Oh wow, that must've been painful

[–] dan@upvote.au 1 points 7 months ago* (last edited 7 months ago)

It was a pretty decent way to get started with coding! This was back in the late 90s in Australia. I didn't have internet access or programming books, so all I could do was teach myself. Being able to record a macro and see the code behind it was extremely useful! :)