mockaton 8.2.10 → 8.2.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -9,8 +9,8 @@ the URL paths. For example, the following mock will be served on `/api/user/1234
|
|
|
9
9
|
```
|
|
10
10
|
my-mocks-dir/api/user/[user-id].GET.200.json
|
|
11
11
|
```
|
|
12
|
-
You don’t need to mock everything.
|
|
13
|
-
`Config.proxyFallback
|
|
12
|
+
You don’t need to mock everything. If you indicate your backend address in
|
|
13
|
+
`Config.proxyFallback` Mockaton will request from it the routes you don’t have mocks for.
|
|
14
14
|
|
|
15
15
|
|
|
16
16
|
By the way, [this browser
|
|
@@ -90,8 +90,7 @@ simulate from the actual backend. In this case, compile your frontend app and
|
|
|
90
90
|
put its built assets in `Config.staticDir`. Then, from the Mockaton dashboard
|
|
91
91
|
you can "Bulk Select" mocks to simulate the complete states you want to demo.
|
|
92
92
|
For bulk-selecting, you just need to add a comment to the mock
|
|
93
|
-
filename
|
|
94
|
-
"Comments" section under the "Filename Convention" for details.
|
|
93
|
+
filename, such as `(demo-part1)`, `(demo-part2)`.
|
|
95
94
|
|
|
96
95
|
|
|
97
96
|
## Motivation
|
package/package.json
CHANGED