WTH can we still only edit yaml code in pre-defined files via UI?

I think the move to more UI is good.
Buuut, why is it still not possible to edit automations or scripts etc. that are located outside the default file.

I am guessing that maaaany users, like myself, are using e.g. the packages approach and have their automations, scripts etc. spread out over multiple yaml files.
We can see them. We can use them. We can trigger, enable and disable them. So why can’t we edit them via UI?

There once was an argument that comments would be disabled. But fine, inform the user that if he starts editing via UI all comments will be deleted. No problem.

If the system can “see” the automation, script etc. the system must be able to edit them :wink:

Thank you