xero-node
Advanced tools
Comparing version 3.0.7 to 3.0.8
@@ -168,2 +168,3 @@ export interface Attachment { | ||
Reference?: string; | ||
Url?: string; | ||
Prepayments?: Prepayment[]; | ||
@@ -170,0 +171,0 @@ Payments?: Payment[]; |
{ | ||
"name": "xero-node", | ||
"version": "3.0.7", | ||
"version": "3.0.8", | ||
"description": "NodeJS Client for the Xero API, supporting Public, Private and Partner Apps", | ||
@@ -5,0 +5,0 @@ "main": "lib/index.js", |
@@ -16,3 +16,3 @@ [![npm version](https://badge.fury.io/js/xero-node.svg)](https://badge.fury.io/js/xero-node) | ||
Version 3 has been rebuilt fron the ground-up using TypeScript, to make it | ||
Version 3 has been rebuilt from the ground-up using TypeScript, to make it | ||
more maintainable and to take advantage of modern JavaScript features. | ||
@@ -222,3 +222,3 @@ | ||
2. A simple and single OAuth flow. Rather than automatically refreshing tokens, the SDK we will expose methods which allow the OAuth methods eg Refreshing Tokens etc. Consideration is also being made to OAuth2. | ||
2. A simple and single OAuth flow. Rather than automatically refreshing tokens, the SDK will expose methods which allow the OAuth methods eg Refreshing Tokens etc. Consideration is also being made to OAuth2. | ||
@@ -225,0 +225,0 @@ 3. Abstracted underlyting OAuth/HTTP lib. This will allow swapping it out if we needed. The SDK won't bleed the OAuth libs exception types onto the consumer when it hits a 500/400 etc. Having a OAuth/HTTP layer will allow reuse and extension to other APIs (Payroll, Expenses etc). |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
204205
4238