Config as Code: editing variables shuffles them around in variables.ocl

[ArturDorochowicz]

Severity

No response

Version

2024.3 (all versions with CaC ?)

Latest Version

None

What happened?

With Config as Code project, editing a variable in the web UI, in most instances, moves it to a completely new place in variables.ocl file. This makes any sort of review and tracking extremely hard. And these are exactly the sort of things that CaC should be enabling and making easier.

The entries in variables.ocl should be normalized when saving, e.g. by sorting alphabetically. I'm truly baffled why this wasn't done this way in the first place.

There's also a smaller issue of empty description properties that appear out of nowhere. They should not be added.

Reproduction

Add a CaC project, add a couple of variables. Commit. Edit values of the variables. Commit. Observe that entries were shuffled around in variables.ocl instead of being changed in place. The diff between commits is very hard to understand.

Error and Stacktrace

No response

More Information

No response

Workaround

No response