rest-client-sdk
Advanced tools
Changelog
6.6.0
AbstractTokenGenator
or call _manageOauthError
TokenGenerator.generateToken
and TokenGenerator.generateToken
might return a Response
instead of a plain object. This should not break anything as the response is handled by the TokenStorage
unless you call directly the TokenGenerator
(which you should not). Returning an object has been deprecated and is only used in the ProvidedTokenGenerator
(which is also deprecated)OauthError.previousError
might be undefinedProvidedTokenGenerator
. You should use one of the oauth2 generator or implement your own custom generator.AbstractTokenGenerator._manageOauthError
is deprecated. You should return the Response
instead : generateToken() {
const body = // … generate body
return fetch(url, {
method: 'POST',
body,
+ });
- }).then((response) => {
- if (response.status < 400) {
- return response;
- }
- return this._manageOauthError(response);
- });
}
Changelog
6.5.2
Fix regression from 6.5.1
: TokenStorage.refreshToken
does now throws an Error anymore if there is no token stored in the storage.
Changelog
6.5.1
TokenStorage.refreshToken
now throws an Error if there is no token stored in the storage.Changelog
6.5.0
Accept Relation.ONE_TO_ONE relation. It is basically handled the same way as MANY_TO_ONE, but has been added for semantic purpose. The comportment may differ later.
Changelog
6.4.1
isUnitOfWorkEnabled
Changelog
6.3.0
Accept Relation.MANY_TO_MANY relation. It is basically handled the same way as ONE_TO_MANY, but has been added for semantic purpose. The comportment may differ later.