bugfix: TrueVault client/api version related errors #23
Conversation
This file contains 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
The usage of the truevault clients was not consistent with the way they are intended to function, and the current API is incompatible with the server's older client version. Updates: * Bumped the server's truevault client to 1.3.0 to match the react app * Updated the react app's usage to pull from the accessToken field as the apiKeyOrAccessToken getter is no longer available; this led to all requests routed through the local server to fail because it was not including the correct token in the header * Updated the react app's handling of document search results as it was referencing a key that no longer exists
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.
The usage of the truevault clients was not consistent with the way they
are intended to function, and the current API is incompatible with the
server's older client version. Updates:
the apiKeyOrAccessToken getter is no longer available; this led to all
requests routed through the local server to fail because it was not
including the correct token in the header
referencing a key that no longer exists