Tolriq

It was discussed above, this is an optional field that servers returns or not at their will. This is still something temporary until there's new proper endpoints anyway and yes...

No 0 would mean 0 as it's a valid value for a total. If there's such need then we can define a well known and documented value like -1 for...

null is not a valid result in OpenSubsonic, never ever. And empty is also against the spec since we define it's a number it can't be empty as it could...

Symfonium is a special case due to the lack of some others API and it does not require the totals so should no really be taken in account, with proper...

As explained before IMO > Break up openapi.json to smaller chunks - and add build step to merge and rebuild it into one file that can be served. Should be...

Your future work was not clear if it was tied to the PR or for future PR. If the split is made before it's ready to merge then no problem.

> (which is my priority). The priority is actually that anything that is merged is stable and maintainable, this is a public documentation of a public API used by many...

> I simply meant some form of pipeline step is needed on every PR to preserve the structural validity of the final generated JSON. In all cases we need a...

@Gr3q Do you intend to still work on this ?

Most don't care about the doc part details so it's hard to get engagement until it's finished. For my case, this work was planned to be done by me to...