@sap-ux/ui5-middleware-fe-mockserver - npm Package Compare versions

Comparing version 2.2.79 to 2.2.80

package.json

 {
   "name": "@sap-ux/ui5-middleware-fe-mockserver",
-  "version": "2.2.79",
+  "version": "2.2.80",
   "description": "SAP Fiori tools - UI5 middleware for the Fiori elements mock server",
@@ -18,3 +18,3 @@ "repository": {
   "dependencies": {
-    "@sap-ux/fe-mockserver-core": "1.4.7"
+    "@sap-ux/fe-mockserver-core": "1.4.8"
   },
@@ -21,0 +21,0 @@ "devDependencies": {

README.md

@@ -19,3 +19,3 @@ # @sap-ux/ui5-middleware-fe-mockserver
 
-In order to use the mock server, the npm module `@sap-ux/ui5-middleware-fe-mockserver` needs to be added as devDependency and ui5.dependencies to `package.json`, and a valid `ui5.yaml` configuration needs to be provided.
+In order to use the mock server, the npm module `@sap-ux/ui5-middleware-fe-mockserver` needs to be added as devDependency to `package.json`, and a valid `ui5.yaml` configuration needs to be provided.
 **Entries in package.json**
@@ -28,7 +28,2 @@
     "@sap-ux/ui5-middleware-fe-mockserver": "^2"
-},
-"ui5": {
-    "dependencies": [
-        "@sap-ux/ui5-middleware-fe-mockserver"
-    ]
 }
@@ -43,3 +38,3 @@
 
-specVersion: '2.0'
+specVersion: '3.0'
 metadata:
@@ -92,5 +87,12 @@ name: <NAME>
 - noETag : disable ETag support on metadata
-- strictKeyMode : disable the default "loose" mode for the key matching, you can try this if the mockserver returns too much data
-- contextBasedIsolation : enable the support of "tenants", by adding /tenant-xxx at the very start of your service call you will be able to work on tenant isolated data.
+- strictKeyMode : disable the default "loose" mode for the key matching.
+By default the mockserver will try many ways to match an entityset with its navigation property, which can result in some rather loose join of data. In case you have a very well defined mockdata and you feel the mockserver is returning too much data, you can enable this feature.
+- contextBasedIsolation : enable the support of "tenants".
+Tenants can be enabled either by using the ?sap-client in your application / request or by prepending /tenant-xxx at the very start of your service call.
+With tenants you will be able to work on tenant isolated data.
 
+On top of the standard json file loading, when using tenants we will automatically try to fetch a specific json data from a file including the tenant ID in the name. 
+For instance if you have an entity called `Product` you can have a `Product.json` file containing the standard data and a `Product-testErrorXXX.json` file for a specific tenant called testErrorXXX.
+If you don't have a tenant specific file, the mockserver will fallback to the standard file.
+
 You can also define static annotation file using the `annotations` entry, each annotation must provide
@@ -97,0 +99,0 @@

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

34657

increased by2%

Number of lines in readme file

119

increased by1.71%

Dependency changes

• + Added@sap-ux/fe-mockserver-core@1.4.8(transitive)

• - Removed@sap-ux/fe-mockserver-core@1.4.7(transitive)

• Updated@sap-ux/fe-mockserver-core@1.4.8