Go lang docs: Add networking instructions & better JSON docs #1087
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
|
Deploy preview for docs ready! ✅ Preview Built with commit abbc3db. |
|
Your preview environment pr-1087-bttf has been deployed. Preview environment endpoints are available at: |
jdorn
approved these changes
Mar 18, 2023
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.
Features and Changes
This updates the current Go lang documentation to include the new example. It also links a simpler existing example that was already created.
I've modified the JSON section of the docs to be more accurate in terms of the JSON users will be passing in.
I've updated the Quick Usage section to help users by including the networking stuff. I think this is important for users to quickly get started.
With both the JSON and Quick Usage sections modified, the docs may look a little redundant, but I thought the JSON section still had relevant info in it so I didn't want to delete it.