Adapt tests for OpenApi

[netconf.git] / restconf / restconf-openapi / src / test / resources / yang-document / device-path-params-test.json

diff --git a/restconf/restconf-openapi/src/test/resources/yang-document/device-path-params-test.json b/restconf/restconf-openapi/src/test/resources/yang-document/device-path-params-test.json
index f6fc795d5b6fe1636b3967546a2a27d8a841fbf6..e814441e0e3f5a3729ba4fb33ca2fd3e958885a5 100644 (file)
--- a/restconf/restconf-openapi/src/test/resources/yang-document/device-path-params-test.json
+++ b/restconf/restconf-openapi/src/test/resources/yang-document/device-path-params-test.json
@@ -3,7 +3,7 @@
   "info": {
     "version": "1.0.0",
     "title": "path-params-test",
-    "description": "We are providing full API for configurational data which can be edited (by POST, PUT, PATCH and DELETE).\nFor operational data we only provide GET API.\n\nFor majority of request you can see only config data in examples. That’s because we can show only one example\nper request. The exception when you can see operational data in example is when data are representing\noperational (config false) container with no config data in it."
+    "description": "We are providing full API for configurational data which can be edited (by POST, PUT, PATCH and DELETE).\nFor operational data we only provide GET API.\n\nFor majority of request you can see only config data in examples. That is because we can show only one example\nper request. The exception when you can see operational data in example is when data are representing\noperational (config false) container with no config data in it."
   },
   "servers": [
     {