Create an Open API spec for the current mock HTTP requests

FYI: the FieldForComponentSuggester service added in https://git.drupalcode.org/project/experience_builder/-/merge_requests/2... should provide a solid foundation one of the API responses we'll need ()

Any takers? Capturing the current mock requests + responses in this way sure would be beneficial, because we'd be able to evolve the OpenAPI schema, which would auto-document the evolution of the communication between client & server!

Looking through the handlers mock, I started the attached OpenAPI spec. It's still a work in progress, but I think it is a good starting point. Let me know what I missed and I can continue updating the spec.

Thanks, @pfrilling! 🤩

Could you convert that to an MR? 🙏 And could you add the SchemaValidationTest that verifies this Open API spec is itself valid? You can pretty much copy/paste it from @larowlan's work at https://git.drupalcode.org/project/decoupled_lb_api/-/commit/84bf1e54153... 😄

How do we validate this, and how do we keep it in sync with the reality? 🤔

We can also write a test that loads the fixtures from UI and validates them AND uses drupalGet to load the controllers and validate them.

Compliance all round 💪

That'd be amazing and what I'd hope for — because in a heterogeneous project like this (geographically, timezone-wise, employment-wise, availability-wise), that's really valuable!