Releases: SAP/cloud-sdk-js
Releases · SAP/cloud-sdk-js
v3.9.0
v3.8.1
v3.8.0
Compatibility Notes
- [connectivity] Remove unused internal functionality around JWT property access, like
userFromJwt
(removed) andaudiences
(changed). (693cd65)
New Functionalities
- [mail-client] Add Support for
Location ID
in destinations of typeMAIL
(8516b7f)
Fixed Issues
- [generator] Don't generate
delete()
,update()
, andgetByKey()
methods in the RequestBuilder of an entity without keys.- @sap-cloud-sdk/[email protected]
- @sap-cloud-sdk/[email protected]
- @sap-cloud-sdk/[email protected]
- @sap-cloud-sdk/[email protected]
- @sap-cloud-sdk/[email protected] (34ef77a)
v3.7.0
Fixed Issues
- [odata-common, odata-v2, odata-v4, generator, generator-common] Do not send
null
values in the request payload for properties that are not set while creating or updating an entity. - [odata-common, odata-v2, odata-v4, generator, generator-common] Fix
RangeError: Maximum call stack size exceeded
error that occurs when updating an entity after callinggetByKey
. (bdcf14f)
v3.6.0
Compatibility Notes
- [connectivity] Proxy configuration is no longer realized through a proxy agent, but with the native axios proxy setting instead. (025b6aa)
- [http-client, connectivity] When using proxies with
@sap-cloud-sdk/connectivity@>=3.6.0
, you must upgrade to@sap-cloud-sdk/http-client@>=3.6.0
. Proxies in@sap-cloud-sdk/connectivity@>=3.6.0
are not compatible with@sap-cloud-sdk/http-client@<3.6.0
. (025b6aa)
Fixed Issues
v3.5.0
Fixed Issues
- [connectivity] Compare
selectionStrategy
inDestinationFetchOptions
based on value instead of reference. (7ed5ceb) - [connectivity] Fix destination caching for destinations from service bindings. The destinations are not cached repeatedly. The function
getDestinationFromServiceBinding()
returnsundefined
for destinations which have expired JWTs. (bf54df0) - [connectivity] Support destinations of type
ClientCertificateAuthentication
without password.- @sap-cloud-sdk/[email protected]
- @sap-cloud-sdk/[email protected] (2277f94)
- [odata-common, odata-v2, odata-v4] Fix OData v2 serialization for
Edm.Decimal
to serialize tostring
. (ee7477c)
v3.4.0
Compatibility Notes
- [connectivity] Deprecate
destinationForServiceBinding()
andPartialDestinationFetchOptions
. UsegetDestinationFromServiceBinding()
andServiceBindingTransformOptions
instead. (bde6463)
New Functionalities
- [connectivity] Always add a name to destinations from service bindings created with
getDestinationFromServiceBinding()
. (db0780f) - [connectivity] Support forwarding of auth tokens for destinations from the destination service, service bindings and environment variables. (bde6463)
Fixed Issues
- [odata-common, odata-v4] Serialize properties of type "Edm.Decimal" to numbers when they are within the safe range and strings when they are not. (431d2a5)
v3.3.0
Compatibility Notes
-
[connectivity] The
expiresIn
property ofauthTokens
on aDestination
can beundefined
. (c09b1d0) -
[connectivity] Deprecate
getAgentConfig()
:- Temporarily use replacement function
getAgentConfigAsync()
. - Rename
getAgentConfigAsync()
togetAgentConfig()
in next major version. (36a01f7)
- Temporarily use replacement function
New Functionalities
- [connectivity] Add option to cache mTLS certificates. (36a01f7)
Improvements
- [connectivity] Do not rely on XSUAA service when caching service tokens. Cache keys are now based on service credentials URL. (0583836)
- [connectivity] Do not rely on the XSUAA service binding to retrieve tenant information when registering destinations. If tenant is unknown and no binding is found, set it to a default value (
'tenant_id'
). (8f54207) - [connectivity] Read mTLS certificates asynchronously. (36a01f7)
Fixed Issues
- [connectivity] Remove dependency to XSUAA service binding when checking whether a JWT was issued by XSUAA for destination retrieval. Now, the
ext_attr.ehancer
property is checked. (6b58354) - [http-client] Do not set default tenant ID in the context of middlewares, if the tenant ID is unknown. In those cases it will be
undefined
from now on. (8f54207)
v3.2.0
New Functionalities
- [connectivity] Enable the use of mTLS certificates for registered destinations on CloudFoundry. (616d77b)
Improvements
- [connectivity] Set the default validity time of the client credentials token cache to 5 minutes instead of never expiring. (782b9e3)
Fixed Issues
- [connectivity, http-client] Forward the user JWT irrespective of the destination authentication type when
forwardAuthToken
is set to true on a destination (56c3f70) - [http-client] Improve CSRF token fetching for large requests. (73ff0ab)
- [odata-common] Remove encoding of keys in the
getEntityKeys()
as it should only happen once ingetResourcePathForKeys()
.Fixes the errorvalue.format is not a function
when executing requests for entities withEdm.Date
type key property. (aa1a4bd) - [resilience] Fix parsing error when the last response in a chain of retries returned undefined.
- @sap-cloud-sdk/[email protected] (234675f)
v3.1.1
Fixed Issues
- [resilience] Fix transpilation on OData generation, where types for 'opossum' could not be found.
- @sap-cloud-sdk/[email protected] (166a16d)