Releases: ordercloud-api/ordercloud-javascript-sdk
Releases · ordercloud-api/ordercloud-javascript-sdk
Regen to API v1.0.197
Added
- SDK up to date with API v1.0.196
Regen to API api v1.0.196, upgrade dependencies, bug fix
Added
- SDK up to date with API v1.0.196
Fixed
OrderCloudErrormodel not exported from public entry point
Security
- Upgraded axios dependency to version 0.21.1
Miscellaneous bug fixes and regen to most recent API
Bug Fixes 🐛
- Don't mutate options object passed to it. The SDK was mutating the options object by deleting
options.filterwhich led to a side-effect for any user relying on the options object. - Cookies were being set to the current path with no way to define your own path. This would cause issues if cookies were being set while the user was not on the root of the domain because that cookie would only be accessible on the path it was created on or any sub-path
- by default cookies are now set at the root
- you can now configure the sdk to set to any path you like. For ex:
Configuration.Set({cookieOptions: { path: 'mypath' }})
- Setting one cookie option would incorrectly remove defaults for the rest
- Models for
searchOnandsortBywere not allowing valid values
Regen SDK ⏩
- SDK now up to date with API v1.0.183
Two bug fixes and catch up to most recent api version
Bug Fixes 🐛
- Cookies were being set to the current path with no way to define your own path. This would cause issues if cookies were being set while the user was not on the root of the domain because that cookie would only be accessible on the path it was created on or any sub-path
- by default cookies are now set at the root
- you can now configure the sdk to set to any path you like. For ex:
Configuration.Set({cookieOptions: { path: 'mypath' }})
- Models for
searchOnandsortBywere not allowing valid values
Regen SDK ⏩
- SDK now up to date with API v1.0.183
Fix bug: don't mutate options object passed to SDK
Bug Fixes 🐛
- Don't mutate options object passed to it. The SDK was mutating the options object by deleting
options.filterwhich led to a side-effect for any user relying on the options object.
Major Release: v4.0.0 (BREAKING)
Please check out the migration guide for full details on how to migrate from version 3.x.x to version 4.x.x
Use new auth url
Breaking Changes 💥
- New auth urls are being used. Previously we used https://auth.ordercloud.io/oauth/token to make auth requests. That same functionality is now a part of the main API. The following updates were made to the SDK configuration as a result:
baseAuthUrlno longer existsbaseApiUrlis updated to exclude apiVersion (default is https://api.ordercloud.io)apiVersionnow exists (default is v1)
SDK has been generated to be in line with API v1.0.165
Revert filters usage and add Tokens.GetValidToken
Breaking Changes 💥
- Found out that the filter types weren't being enforced unless inlined, essentially rendering the feature useless. Reverting to the way filter used to work previously where the keys are the properties to filter on (dot referenced string for nested xp values)
New Feature ✨
- Added
Tokens.GetValidToken. If the token exists and is valid, it will return it. If it doesn't exist or is invalid it will attempt to refresh the token and return that.
searchType and update dependency superagent
New Feature ✨
- New
searchTypeparameter forv1/me/productsand premium-search-enabledv1/products. See this blog post for details: https://ordercloud.io/blog/new-for-premium-search - update dependency superagent to latest (version 5.2.2)
updates for searchType from API 1.0.151
✨ New Feature
- New
searchTypeparameter forv1/me/productsand premium-search-enabledv1/products. See this blog post for details: https://ordercloud.io/blog/new-for-premium-search