intesys / ymock Goto Github PK

The app should be able to import its config in JSON format.

As different requests can be made to the same endpoint, based on the data provided during user interaction (i.e. different payloads, maybe with specific values, sent on a submit action), the app should provide the option to serve a specific mock variant in response to a specific request.

The app should validate the mocks based on an OpenAPI spec.

The app should be able to enable/disable mocks at runtime.

The user should be able to set a one-time override for a mock; after running exactly once, the override would restore the default mock.

The app should persist its UI configurations via localStorage or similar.

Self-explanatory.

The override should be applied permanently by default, and continue to operate until the user disables it.

If the override is of the temporary type, it should run exactly once (see #4 (comment))

The user should be able to edit the mocks directly from the app UI.

The app should be able to export its config in JSON format.

The app should provide a minimal, non-intrusive UI (such as the "proactive chat" buttons we see on many websites), always visible over the host app's UI. When interacted with, this UI will summon the app in a new window.