fix: add api details for management API to example, remove token requirement. #31
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
In order to have this client function correctly facing the management API both the api_url and api_version must be specified. And API token is not required for the managment API, just an OAuth Token
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.
In order to have this client function correctly facing the management API both the api_url and api_version must be specified.
API token is not required for the management API, just an OAuth Token
Pull request type
Jira Link: INT-
How to test this PR
Create an OAuth Token and include it in place of OAUTH_TOKEN, and run the example.
What is the new behavior?
This example previously did not work out of the box because the API was not properly specified for management. Generally, information on how to use this gem is under documented in this repository and on the main storyblok documentation and most examples will not run out of the box due to this problem. I suspect there are similar issues on the content API side but this is the only one I've tested and gotten working.
Other information
The ruby documentation on the Storyblok site generally will not run out of the box due to these issues.