oauth2 related fixes #4309
Merged
oauth2 related fixes #4309
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lohxt1
changed the title
…esponse and clear timeline are 2 different things, clear redux state after clearing oauth2 credentials cache
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
~ update ui when the oauth2 credentials cache is cleared
~ oauth2 credentials token expiration check should be done only if the
expires_inprop is present~
clear responseandclear timelineactions seperation in response pane tab~ seperate util functions for
bruno-lang/v2~ add default values for
autoFetchTokenandautoRefreshTokenbefore the.toString()operationthis ensures that pre-existing oauth2 configurations that lack these newly introduced values do not cause issues.
~ use
safeParseJson