[LadySolveig]

Pull Request for Issue #

Summary of Changes

Testing Instructions

Documentation Changes Required

[HermanPeeren]

Hi @renekreijveld and @LadySolveig, thanks for the work on the Bruno collection and the tests!

What we did with the main branch in the repo, and a proposal for the bruno branch.

What's new in this repo

• src/joomla-ws-api.json is the latest and most complete OpenAPI spec of the Joomla 6.2 Web Services API: 235 operations, checked by CI on every pull request (validity, lint, quality, and the routes of Joomla itself). It's released as 6.2.1.
• Roland's PhpStorm HTTP Client collection (Add a PhpStorm HTTP Client collection, generated at build time and published as a release file and a branch #4) is generated from the spec. It's a release file (joomla-ws-api-<version>-phpstorm.zip) and the phpstorm branch, which updates automatically on every change of main.

Proposal for the bruno branch

• The same for Bruno: a generator in main that writes the collection from the spec, a -bruno.zip in each release, and the bruno branch updated automatically. The collection then always matches the spec, including the endpoints that are missing now.
• The generator makes the file and folder names itself, without spaces, so the renaming in this PR isn't needed.
• Martina's tests and pre-request data are valuable, and the generator shouldn't overwrite them. My idea: keep them in main per operation, for instance scripts/bruno/tests/<operationId>.js, and let the generator add them to the matching request.

Questions

1. René: did you make the current collection with a generator, or with Bruno's OpenAPI import? If there's a script, we could start from it.
2. Martina: would the tests per operation in main work for you? Or do you see a better way to keep them next to a generated collection?

[HermanPeeren]

Closed after discussion on Mattermost and rest of that thread. No need for a separate Bruno collection anymore.