@interledger/open-payments - npm Package Compare versions

Comparing version 3.1.0 to 3.2.0

dist/client/index.d.ts

@@ -6,3 +6,2 @@ /// <reference types="node" />
 import { IncomingPaymentRoutes } from './incoming-payment';
-import { ILPStreamConnectionRoutes } from './ilp-stream-connection';
 import { PaymentPointerRoutes } from './payment-pointer';
@@ -63,3 +62,2 @@ import { AxiosInstance } from 'axios';
 export interface UnauthenticatedClient {
-    ilpStreamConnection: ILPStreamConnectionRoutes;
     paymentPointer: PaymentPointerRoutes;
@@ -66,0 +64,0 @@ }

dist/client/index.js

@@ -12,3 +12,2 @@ "use strict";
 const incoming_payment_1 = require("./incoming-payment");
-const ilp_stream_connection_1 = require("./ilp-stream-connection");
 const payment_pointer_1 = require("./payment-pointer");
@@ -42,7 +41,2 @@ const requests_1 = require("./requests");
     return {
-        ilpStreamConnection: (0, ilp_stream_connection_1.createILPStreamConnectionRoutes)({
-            axiosInstance,
-            openApi: resourceServerOpenApi,
-            logger
-        }),
         paymentPointer: (0, payment_pointer_1.createPaymentPointerRoutes)({
@@ -69,7 +63,2 @@ axiosInstance,
         }),
-        ilpStreamConnection: (0, ilp_stream_connection_1.createILPStreamConnectionRoutes)({
-            axiosInstance,
-            openApi: resourceServerOpenApi,
-            logger
-        }),
         paymentPointer: (0, payment_pointer_1.createPaymentPointerRoutes)({
@@ -76,0 +65,0 @@ axiosInstance,

dist/openapi/generated/resource-server-types.d.ts

@@ -20,20 +20,2 @@ /**
     };
-    "/connections/{id}": {
-        /**
-         * *NB* Use server url specific to this path.
-         *
-         * Fetch new connection credentials for an ILP STREAM connection.
-         *
-         * A connection is an ephemeral resource that is created to accommodate new incoming payments.
-         *
-         * A new set of credential will be generated each time this API is called.
-         */
-        get: operations["get-ilp-stream-connection"];
-        parameters: {
-            path: {
-                /** Sub-resource identifier */
-                id: components["parameters"]["id"];
-            };
-        };
-    };
     "/incoming-payments": {
@@ -224,2 +206,9 @@ /** List all incoming payments on the payment pointer */
         /**
+         * Public Incoming Payment
+         * @description An **incoming payment** resource with public details.
+         */
+        "public-incoming-payment": {
+            receiveAmount?: external["schemas.yaml"]["components"]["schemas"]["amount"];
+        };
+        /**
          * Outgoing Payment
@@ -339,5 +328,9 @@ * @description An **outgoing payment** resource represents a payment that will be, is currently being, or has previously been, sent from the payment pointer.
         /** @description The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. */
-        signature: string;
+        signature: components["parameters"]["optional-signature"];
         /** @description The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message.  Each member describes a single message signature.  The member's key is the label that uniquely identifies the message signature within the context of the HTTP message.  The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label.  The following components MUST be included: - "@method" - "@target-uri" - "authorization".  When the message contains a request body, the covered components MUST also include the following: - "content-digest"  The keyid parameter of the signature MUST be set to the kid value of the JWK.      See [ietf-httpbis-message-signatures](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-message-signatures#section-4.1) for more details. */
-        "signature-input": string;
+        "signature-input": components["parameters"]["optional-signature-input"];
+        /** @description The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. */
+        "optional-signature": string;
+        /** @description The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message.  Each member describes a single message signature.  The member's key is the label that uniquely identifies the message signature within the context of the HTTP message.  The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label.  The following components MUST be included: - "@method" - "@target-uri" - "authorization".  When the message contains a request body, the covered components MUST also include the following: - "content-digest"  The keyid parameter of the signature MUST be set to the kid value of the JWK.      See [ietf-httpbis-message-signatures](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-message-signatures#section-4.1) for more details. */
+        "optional-signature-input": string;
     };
@@ -378,29 +371,2 @@ }
     };
-    /**
-     * *NB* Use server url specific to this path.
-     *
-     * Fetch new connection credentials for an ILP STREAM connection.
-     *
-     * A connection is an ephemeral resource that is created to accommodate new incoming payments.
-     *
-     * A new set of credential will be generated each time this API is called.
-     */
-    "get-ilp-stream-connection": {
-        parameters: {
-            path: {
-                /** Sub-resource identifier */
-                id: components["parameters"]["id"];
-            };
-        };
-        responses: {
-            /** Connection Found */
-            200: {
-                content: {
-                    "application/json": components["schemas"]["ilp-stream-connection"];
-                };
-            };
-            /** Connection Not Found */
-            404: unknown;
-        };
-    };
     /** List all incoming payments on the payment pointer */
@@ -622,5 +588,5 @@ "list-incoming-payments": {
                 /** The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message.  Each member describes a single message signature.  The member's key is the label that uniquely identifies the message signature within the context of the HTTP message.  The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label.  The following components MUST be included: - "@method" - "@target-uri" - "authorization".  When the message contains a request body, the covered components MUST also include the following: - "content-digest"  The keyid parameter of the signature MUST be set to the kid value of the JWK.      See [ietf-httpbis-message-signatures](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-message-signatures#section-4.1) for more details. */
-                "Signature-Input": components["parameters"]["signature-input"];
+                "Signature-Input"?: components["parameters"]["optional-signature-input"];
                 /** The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. */
-                Signature: components["parameters"]["signature"];
+                Signature?: components["parameters"]["optional-signature"];
             };
@@ -632,3 +598,3 @@ };
                 content: {
-                    "application/json": components["schemas"]["incoming-payment-with-connection"];
+                    "application/json": Partial<components["schemas"]["incoming-payment-with-connection"]> & Partial<components["schemas"]["public-incoming-payment"]>;
                 };
@@ -635,0 +601,0 @@ };

package.json

 {
   "name": "@interledger/open-payments",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Tools for interacting with the Open Payments API",
@@ -28,4 +28,4 @@ "author": "Interledger Tech Team <[e-mail]>",
   "dependencies": {
-    "@interledger/http-signature-utils": "1.0.4",
-    "@interledger/openapi": "1.0.3",
+    "@interledger/http-signature-utils": "1.1.0",
+    "@interledger/openapi": "1.1.0",
     "axios": "^1.3.4",
@@ -32,0 +32,0 @@ "base64url": "^3.0.1",

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

Worsened metrics

Total package byte prevSize

223880

decreased by-0.41%

Number of package files

34

decreased by-5.56%

Lines of code

2514

decreased by-2.6%

Dependency changes

• + Added@interledger/http-signature-utils@1.1.0(transitive)

• + Added@interledger/openapi@1.1.0(transitive)

• - Removed@interledger/http-signature-utils@1.0.4(transitive)

• - Removed@interledger/openapi@1.0.3(transitive)

• Updated@interledger/http-signature-utils@1.1.0

• Updated@interledger/openapi@1.1.0