Support the user providing an OpenAPI schema, and automatically populating mock responses with stable, random data.

Stable, meaning that the random values are generated using the request parameters, so that identical requests receive identical responses (without having to store any of the randomly generated data).

Users should be able to add stable random data to any mocked response in a manner they see fit. For instance, if a response is defined as a template using a templating engine, the service could allow a specialized template interpolation for inserting a stable random value of a particular type (i.e., faker values).

For this delivery, random values are seeded from the plain URL string. Write this extensibly if possible for future user configuration of randomness sources.

Create an API mocking server that can serve user-defined mock payloads by matching against incoming requests and loading responses from storage.

Request matching logic should be written extensibly, and for this delivery it must only naively match the URL path.

For this delivery, mock responses are static values, defined by the user via a user interface.

Storage of configuration should be written extensibly, but the only implementation to be delivered right now is file-based.