@interledger/[email protected]

Patch Changes

• c9e1d15: Changes return type of outgoingPayment.create to OutgoingPaymentWithSpentAmounts to reflect correct return type.

@interledger/[email protected]

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/[email protected]

Minor Changes

• aa21d26: Adding functionality to parse error objects from Open Payments API responses, and expose new code field in OpenPaymentsClientError.

@interledger/[email protected]

Patch Changes

• 73e2c52: Export OutgoingPaymentWithSpentAmounts

@interledger/[email protected]

Minor Changes

• 5c0e768: Changes POST /outgoing-payment return to new 'outgoing-payment-with-spent-amounts' type with grantSpentDebitAmount and grantSpentReceiveAmount

@interledger/[email protected]

Minor Changes

• 8950c21: Replace axios with ky (a wrapper around native fetch)
• 1bf703c: Adding validateResponses flag to Open Payments client initialization functions.
  This flag enables or disables response validation against the Open Payments OpenAPI specs (via the @interledger/openapi package).

@interledger/[email protected]

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/[email protected]

Patch Changes

• dd7fb76: - Exporting OpenAPIValidatorMiddlewareError from package

@interledger/[email protected]

Patch Changes

• Updated dependencies [dd7fb76]
  • @interledger/[email protected]

@interledger/[email protected]

Major Changes

• 6dde8b2: Changes to the createValidatorMiddleware behaviour:

  • The middleware now throws a OpenAPIValidatorMiddlewareError instead of directly using Koa's ctx.throw function. This error class has message and status 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 uses process.env.NODE_ENV to determine whether to validate the response or not.