fix(merge-specs): Use objects instead of associative arrays to fix empty JSON objects

[provokateurin]

#225

Otherwise {} from JSON will turn into [] in PHP and then into [] in JSON which is not valid.

[nickvergessen]

Is this testable? :-X

[provokateurin]

I'll open a draft PR in documentation, then you can modify it to use openapi-extractor from path and check the diff.

[provokateurin]

You can now test it with nextcloud/documentation#12887.
The way I tested it was generating the merged spec on the current master branch, copying it somewhere else, checking out the branch, generating it again (you need to adjust the path to merge-specs.php first) and then diffing the new with the previous spec.

[provokateurin]

But on this topic, I was thinking of maybe adding the merged spec to the server repo (in the root folder) and then we can also run it as part of the CI here to check for any diffs or failures. It wouldn't even need any adjustments in this repo, just in server.
This would also make the specifications more accessible, because for standalone apps they are in the root folder, but for server it's more complicated and less obvious for people who don't develop Nextcloud directly.

[nickvergessen]

yeah that's what I meant

[provokateurin]

nextcloud/server#51674

[provokateurin]

Diff can be seen now: https://github.com/nextcloud/openapi-extractor/actions/runs/14041462379/job/39312409619?pr=227

[provokateurin]

@nickvergessen can you check again, so we can merge the PR and close the topic?

[nickvergessen]

I don't have time at the moment, so just merge it I guess?