Skip to content

Fix documentation bugs #1224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 28, 2017
Merged

Fix documentation bugs #1224

merged 1 commit into from
Apr 28, 2017

Conversation

stefansundin
Copy link
Contributor

Hello again, I am back with some more documentation fixes! :)

This time I went out of my way to hunt for both big and small issues. Let me know if you find any mistakes in my corrections.

Additionally, there are some bugs in the generated documentation. Since it appears the tool that is actually used to generate https://docs.aws.amazon.com/sdk-for-go/api/ is not open source, I couldn't actually fix these bugs, but here are some screenshots:

Ugly header

screen shot 2017-04-21 at 23 05 45

List not rendered

screen shot 2017-04-21 at 23 05 35

List not rendered

screen shot 2017-04-21 at 23 06 08

xibz
xibz previously requested changes Apr 24, 2017
Copy link
Contributor

@xibz xibz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @stefansundin, I have a couple minor comments. But overall it looks great! Thank you for taking the time to do this.

@@ -4029,6 +4029,7 @@ func (s *DeliveryChannel) SetSnsTopicARN(v string) *DeliveryChannel {
// The status of a specified delivery channel.
//
// Valid values: Success | Failure
//
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is autogenerated.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For these i suggest just removing the api.go files from the PR. We can upstream these doc issues to the service teams

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jasdel let me know when the api.go fixes have been sent upstream, and then I will undo the changes from the PR.

@@ -2974,7 +2974,7 @@ type AddPermissionInput struct {
_ struct{} `type:"structure"`

// The AWS Lambda action you want to allow in this statement. Each Lambda action
// is a string starting with lambda: followed by the API name . For example,
// is a string starting with lambda: followed by the API name. For example,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here.

@stefansundin
Copy link
Contributor Author

I just undid the api.go changes. Don't forget to send them upstream. ;)

Also, don't forget to fix the markdown lists that I took screenshots of.

@jasdel
Copy link
Contributor

jasdel commented Apr 28, 2017

Thanks for pointing that out again. It looks like the markdown generator the SDK is using to convert the README.md file to an HTML page for "https://docs.aws.amazon.com/sdk-for-go/api/" isn't generating lists correctly at all. I'll take a look at the rules we have setup for that and see about getting this fixed.

@jasdel jasdel dismissed xibz’s stale review April 28, 2017 21:04

updates made

@jasdel jasdel merged commit 301ea4d into aws:master Apr 28, 2017
jasdel added a commit to jasdel/aws-sdk-go that referenced this pull request Apr 28, 2017
Cleaned up the README's header style and fixup to the godoc styling.

Related aws#1224
jasdel added a commit to jasdel/aws-sdk-go that referenced this pull request Apr 28, 2017
Cleaned up the README's header style and fixup to the godoc styling.

Related aws#1224
jasdel added a commit that referenced this pull request Apr 29, 2017
Cleaned up the README's header style and fixup to the godoc styling.

Related #1224
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants