feat: add refreshTokenHandler option #7237
Conversation
🦋 Changeset detectedLatest commit: 6810360 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| [ADDED] new option to the `middlewareModule` - `refreshTokenHandler`. | ||
| This special handler can be used to handle 401 errors and refresh the token. | ||
| It is called before the generic `errorHandler`. | ||
| By default, it thrown an error which is being caught by the `errorHandler` and rethrown. |
There was a problem hiding this comment.
I think that some small diagram (even ascii) with the sequence will be useful here. Or maybe we can somehow rephrase this sentence, I think I would not understand it without my knowledge about how it works. Something like an explanation that by default we are not able to predict the mechanism of token refresh because of differences in different services therefore we do not provide any default behavior, we simply push the error to the errorHandler without any further actions.
| methodName, | ||
| url, | ||
| params, | ||
| config, |
There was a problem hiding this comment.
Is this a module config? Or what kind of config? Will I have some docs in TS? If not maybe lets explain the injected object here?
|
Converted to draft as I'm still not convinced that it is the best solution. |
|
🔗 Linked issue
❓ Type of change
📚 Description
Adds a new optional property
refreshTokenHandlerto themiddlewareModule📝 Checklist