@sasjs/api 0.3.1 → 0.4.0

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 CHANGED
@@ -9,7 +9,7 @@ The plan that this package implements is tracked in `sasjs/cli#1550`.
9
9
 
10
10
  ## What is in it
11
11
 
12
- **The route table** (`ROUTES`, `findRoute`) is every operation in the API - 31 paths, 60 operations - derived from `spec/swagger.yaml` by `npm run sync:routes`.
12
+ **The route table** (`ROUTES`, `findRoute`) is every operation in the API - 31 paths, 61 operations - derived from `spec/swagger.yaml` by `npm run sync:routes`.
13
13
  The statuses come from that document and nowhere else: the overlay cannot add one, and an overlay entry naming a status the document does not state fails the build rather than describing a wish.
14
14
  The document cannot say everything a host needs, so the reviewed overlay adds the body each response carries, the capability a route needs, and whether this package implements it.
15
15
  Where the document is wrong, it is corrected in `sasjs/server` and re-vendored here - never worked around in the overlay.
package/build/browser.js CHANGED
@@ -1,4 +1,4 @@
1
- /* @sasjs/api 0.3.1 - the SASjs Server API, for a service worker. https://github.com/sasjs/api */
1
+ /* @sasjs/api 0.4.0 - the SASjs Server API, for a service worker. https://github.com/sasjs/api */
2
2
  "use strict";
3
3
  var SASjsApi = (() => {
4
4
  var __defProp = Object.defineProperty;
@@ -744,6 +744,42 @@ var SASjsApi = (() => {
744
744
  }
745
745
  ]
746
746
  },
747
+ {
748
+ id: "DELETE /SASjsApi/drive/deploy",
749
+ method: "DELETE",
750
+ path: "/SASjsApi/drive/deploy",
751
+ tag: "Drive",
752
+ summary: "Remove an app stream entry",
753
+ params: [
754
+ {
755
+ name: "appLoc",
756
+ in: "body",
757
+ required: true,
758
+ type: "string"
759
+ },
760
+ {
761
+ name: "streamServiceName",
762
+ in: "body",
763
+ required: true,
764
+ type: "string"
765
+ }
766
+ ],
767
+ requestBodies: ["application/json"],
768
+ responses: [
769
+ {
770
+ status: 200,
771
+ description: "Ok"
772
+ },
773
+ {
774
+ status: 400,
775
+ description: "Invalid Format"
776
+ },
777
+ {
778
+ status: 404,
779
+ description: "No such app stream entry"
780
+ }
781
+ ]
782
+ },
747
783
  {
748
784
  id: "POST /SASjsApi/drive/deploy",
749
785
  method: "POST",
@@ -2094,6 +2130,15 @@ var SASjsApi = (() => {
2094
2130
  "POST /SASjsApi/drive/deploy/upload": {
2095
2131
  implemented: false
2096
2132
  },
2133
+ // Unpublishing is the counterpart of the two above and lands with them: the
2134
+ // document in sasjs/server states it (sasjs/server#543), so a host may answer
2135
+ // it in the meantime, but this package cannot until the publish side it would
2136
+ // invert is implemented here. The statuses are the document's; `404` is a pair
2137
+ // - the registry name and the appLoc it was published from - that matches no
2138
+ // entry, and the drive's content is deliberately left alone.
2139
+ "DELETE /SASjsApi/drive/deploy": {
2140
+ implemented: false
2141
+ },
2097
2142
  // The lockout and the provider failure are answered before the package is
2098
2143
  // consulted (routes/web/web.ts in sasjs/server).
2099
2144
  "POST /SASLogon/login": {
@@ -400,6 +400,42 @@ exports.GENERATED_ROUTES = [
400
400
  }
401
401
  ]
402
402
  },
403
+ {
404
+ id: 'DELETE /SASjsApi/drive/deploy',
405
+ method: 'DELETE',
406
+ path: '/SASjsApi/drive/deploy',
407
+ tag: 'Drive',
408
+ summary: 'Remove an app stream entry',
409
+ params: [
410
+ {
411
+ name: 'appLoc',
412
+ in: 'body',
413
+ required: true,
414
+ type: 'string'
415
+ },
416
+ {
417
+ name: 'streamServiceName',
418
+ in: 'body',
419
+ required: true,
420
+ type: 'string'
421
+ }
422
+ ],
423
+ requestBodies: ['application/json'],
424
+ responses: [
425
+ {
426
+ status: 200,
427
+ description: 'Ok'
428
+ },
429
+ {
430
+ status: 400,
431
+ description: 'Invalid Format'
432
+ },
433
+ {
434
+ status: 404,
435
+ description: 'No such app stream entry'
436
+ }
437
+ ]
438
+ },
403
439
  {
404
440
  id: 'POST /SASjsApi/drive/deploy',
405
441
  method: 'POST',
@@ -77,6 +77,15 @@ exports.OVERLAY = {
77
77
  'POST /SASjsApi/drive/deploy/upload': {
78
78
  implemented: false
79
79
  },
80
+ // Unpublishing is the counterpart of the two above and lands with them: the
81
+ // document in sasjs/server states it (sasjs/server#543), so a host may answer
82
+ // it in the meantime, but this package cannot until the publish side it would
83
+ // invert is implemented here. The statuses are the document's; `404` is a pair
84
+ // - the registry name and the appLoc it was published from - that matches no
85
+ // entry, and the drive's content is deliberately left alone.
86
+ 'DELETE /SASjsApi/drive/deploy': {
87
+ implemented: false
88
+ },
80
89
  // The lockout and the provider failure are answered before the package is
81
90
  // consulted (routes/web/web.ts in sasjs/server).
82
91
  'POST /SASLogon/login': {
@@ -1 +1 @@
1
- {"version":3,"file":"generated.d.ts","sourceRoot":"","sources":["../../../src/routes/generated.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AACH,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,aAAa,CAAA;AAEjD,eAAO,MAAM,gBAAgB,EAAE,cAAc,EA6oD5C,CAAA"}
1
+ {"version":3,"file":"generated.d.ts","sourceRoot":"","sources":["../../../src/routes/generated.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AACH,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,aAAa,CAAA;AAEjD,eAAO,MAAM,gBAAgB,EAAE,cAAc,EAirD5C,CAAA"}
@@ -397,6 +397,42 @@ export const GENERATED_ROUTES = [
397
397
  }
398
398
  ]
399
399
  },
400
+ {
401
+ id: 'DELETE /SASjsApi/drive/deploy',
402
+ method: 'DELETE',
403
+ path: '/SASjsApi/drive/deploy',
404
+ tag: 'Drive',
405
+ summary: 'Remove an app stream entry',
406
+ params: [
407
+ {
408
+ name: 'appLoc',
409
+ in: 'body',
410
+ required: true,
411
+ type: 'string'
412
+ },
413
+ {
414
+ name: 'streamServiceName',
415
+ in: 'body',
416
+ required: true,
417
+ type: 'string'
418
+ }
419
+ ],
420
+ requestBodies: ['application/json'],
421
+ responses: [
422
+ {
423
+ status: 200,
424
+ description: 'Ok'
425
+ },
426
+ {
427
+ status: 400,
428
+ description: 'Invalid Format'
429
+ },
430
+ {
431
+ status: 404,
432
+ description: 'No such app stream entry'
433
+ }
434
+ ]
435
+ },
400
436
  {
401
437
  id: 'POST /SASjsApi/drive/deploy',
402
438
  method: 'POST',
@@ -1 +1 @@
1
- {"version":3,"file":"overlay.d.ts","sourceRoot":"","sources":["../../../src/routes/overlay.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,OAAO,KAAK,EAAE,UAAU,EAAE,UAAU,EAAE,MAAM,aAAa,CAAA;AAEzD,MAAM,WAAW,YAAY;IAC3B,YAAY,CAAC,EAAE,UAAU,EAAE,CAAA;IAC3B,WAAW,CAAC,EAAE,OAAO,CAAA;IACrB;;;;;;;OAOG;IACH,aAAa,CAAC,EAAE,MAAM,EAAE,CAAA;IACxB;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAA;CACpC;AAED,kFAAkF;AAClF,eAAO,MAAM,gBAAgB,EAAE,MAAM,CAAC,MAAM,EAAE,UAAU,EAAE,CAczD,CAAA;AAYD,eAAO,MAAM,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,YAAY,CAoFhD,CAAA;AAED,wEAAwE;AACxE,eAAO,MAAM,OAAO,EAAE,UAAU,EAA8C,CAAA"}
1
+ {"version":3,"file":"overlay.d.ts","sourceRoot":"","sources":["../../../src/routes/overlay.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,OAAO,KAAK,EAAE,UAAU,EAAE,UAAU,EAAE,MAAM,aAAa,CAAA;AAEzD,MAAM,WAAW,YAAY;IAC3B,YAAY,CAAC,EAAE,UAAU,EAAE,CAAA;IAC3B,WAAW,CAAC,EAAE,OAAO,CAAA;IACrB;;;;;;;OAOG;IACH,aAAa,CAAC,EAAE,MAAM,EAAE,CAAA;IACxB;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAA;CACpC;AAED,kFAAkF;AAClF,eAAO,MAAM,gBAAgB,EAAE,MAAM,CAAC,MAAM,EAAE,UAAU,EAAE,CAczD,CAAA;AAYD,eAAO,MAAM,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,YAAY,CA6FhD,CAAA;AAED,wEAAwE;AACxE,eAAO,MAAM,OAAO,EAAE,UAAU,EAA8C,CAAA"}
@@ -74,6 +74,15 @@ export const OVERLAY = {
74
74
  'POST /SASjsApi/drive/deploy/upload': {
75
75
  implemented: false
76
76
  },
77
+ // Unpublishing is the counterpart of the two above and lands with them: the
78
+ // document in sasjs/server states it (sasjs/server#543), so a host may answer
79
+ // it in the meantime, but this package cannot until the publish side it would
80
+ // invert is implemented here. The statuses are the document's; `404` is a pair
81
+ // - the registry name and the appLoc it was published from - that matches no
82
+ // entry, and the drive's content is deliberately left alone.
83
+ 'DELETE /SASjsApi/drive/deploy': {
84
+ implemented: false
85
+ },
77
86
  // The lockout and the provider failure are answered before the package is
78
87
  // consulted (routes/web/web.ts in sasjs/server).
79
88
  'POST /SASLogon/login': {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sasjs/api",
3
- "version": "0.3.1",
3
+ "version": "0.4.0",
4
4
  "description": "The SASjs Server API, described once - a generated route table, the services behind it, and the conformance corpus both hosts run",
5
5
  "license": "MIT",
6
6
  "author": "SASjs",