apimock-rs (former json-responder) 1.1: dynamic path resolution

I released json-responder 1.1.0.

apimokka / apimock-rs

HTTP(S) mock server. Drop JSON files into a folder and your API immediately exists.

apimock-rs (API Mock)

Build a working REST API in seconds — without a backend.
Frontend blocked by an unfinished backend Need stable API responses for UI tests or offline development ?
Drop JSON files into a folder and your API immediately exists.

Mock APIs easily 🎈 — just JSON and go

If you’re building or testing APIs, this tool makes mocking painless. It’s super fast, efficient, and flexible when you need it to be. All you have to do to start up is just use folders and JSON without any config set.

• ❄️ Zero-config start.
• 🌬️ Fast to boot, light on memory.
• 🪄 File-based and rule-based matching. Scripting supported.

apimock-rs handles real project scale

As your project grows, your mock API grows, too. Large mock datasets often cause problems:

• Slow startup
• High memory usage
• Crashes during UI testing
• Unstable CI runs

When to use ?

• The backend is not…

View on GitHub

This release contains new feature to resolve path dynamically when dyn_data_dir is activated.

It means the server automatically returns .json / .json5 responses under dyn_data_dir.

Supposed that there is:

json-responder-data (as `dyn_data_dir`)
├── a
│   └── b
│       └── c.json5
└── a.json

the responses at requests are:

request path	response content
/a	a.json
/a/b	(HTTP 404)
/a/b/c	c.json5

Now you don't have to write in config all paths you want to use in API tests ☺

Comments

[nabbisen]

Renamed to apimock-rs. Now more than returning JSON data.

github.com/nabbisen/apimock-rs