Schema property order

[imaretic]

Schema properties in OGraf manifest are contained within the schema JSON object, which means there is no defined order in which the controller UI will read and render input elements to the user.

This can be inconvenient, as less important (or optional) properties may appear before more important ones, making the interface harder to use.

A potential solution to this problem could be to add an optional order property to each schema property item.

[didikunz]

That's a good point. Another solution could be to just let the UI render the controls from top to bottom, let the order in which the properties are listed be the implicit order number. AFAIK that is also the way it's meant to be in GDD.

[nytamin]

I think this would be a good addition. To further add to the context, the order of properties in a json-object is implied only, and not guaranteed to be unchanged.

"An object is an unordered collection of zero or more name/value pairs, where a name is a string and a value is a string, number, boolean, null, object, or array." (Source RFC 7159)

[nytamin]

Notes from Working Group meeting 2025-10-29:

Conclusion: Let's add an optional order property