Could I ask some clarification on the comment in Improve the language API by @jmooring suggesting that .Language.Weight may be deprecated soon, as neither PAGE.Version nor PAGE.Role have the weight method. On the OP of the issue, Site and page methods are indicated.
Would it be possible to reconsider and not deprecate Weight for languages (at least for the site method, ideally for the page one too), even though it is not currently consistent with other dimensions?
We currently rely on languages weight for two use cases:
.Rotateon language navigators, where sorting by weight instead of lexicographically allows to keep a consistent order (regardless of label, addition or enablement of languages).- A summary of languages translation completion, as a data file or visual representation (dashboard similar to services such as Weblate), where consistent sort order is handy.
I am not requesting for the following to be implemented, but some methods to access other dimensions weight is probably convenient as well? At least for versions, several use cases can be imagined (e.g. not using semantic versioning, referring to the latest main or stable content when the versions keys have a different logic). Probably for roles too.
Or maybe I misunderstood the intention behind these deprecations? TIA!