Releases: interledger/open-payments
Releases · interledger/open-payments
@interledger/open-payments@6.13.1
Patch Changes
- c9e1d15: Changes return type of outgoingPayment.create to OutgoingPaymentWithSpentAmounts to reflect correct return type.
@interledger/open-payments@6.13.0
Minor Changes
- d7535db: - Adding debug logs during client initialization
- Adding debug logs for requests and responses in the http client
- Making log level
silent
by default
@interledger/open-payments@6.12.0
Minor Changes
- aa21d26: Adding functionality to parse error objects from Open Payments API responses, and expose new
code
field inOpenPaymentsClientError
.
@interledger/open-payments@6.11.1
Patch Changes
- 73e2c52: Export OutgoingPaymentWithSpentAmounts
@interledger/open-payments@6.11.0
Minor Changes
- 5c0e768: Changes POST /outgoing-payment return to new 'outgoing-payment-with-spent-amounts' type with grantSpentDebitAmount and grantSpentReceiveAmount
@interledger/open-payments@6.10.0
@interledger/open-payments@6.9.0
Minor Changes
- 3bbd59a: changes POST /outgoing-payment body and client's outgoingPayment.create args to accept incomingPayment and debitAmount as alternative to quoteId. This supports creating outgoing payments directly from incoming payments instead of from a quote.
@interledger/openapi@2.0.1
Patch Changes
- dd7fb76: - Exporting
OpenAPIValidatorMiddlewareError
from package
@interledger/open-payments@6.8.2
Patch Changes
- Updated dependencies [dd7fb76]
- @interledger/openapi@2.0.1
@interledger/openapi@2.0.0
Major Changes
-
6dde8b2: Changes to the
createValidatorMiddleware
behaviour:- The middleware now throws a
OpenAPIValidatorMiddlewareError
instead of directly using Koa'sctx.throw
function. This error class hasmessage
andstatus
properties that describe the exact validation error as well as the status code that should be thrown. - The middleware now takes in an optional
validationOptions
argument that determines whether to validate just the request, the response or both. By default, both are validated, and the middleware no longer usesprocess.env.NODE_ENV
to determine whether to validate the response or not.
- The middleware now throws a