Skip to content
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

Small documentation fixes #2

Closed
wants to merge 2 commits into from
Closed

Small documentation fixes #2

wants to merge 2 commits into from

Conversation

zachmandeville
Copy link

These are a couple fixes for issues that came up when exploring this code. In the readme for the exporter, there is a reference to an example output that does not show due to how github parses org files. I removed the #+RESULTS tag so that the output shows. I also removed instances where ... appeared at the end of a function comment, as the go tooling ignores commented lines after these dots.

it seems when a comment ends with a period, the reest of the comment is
ignored, which defeats the purpose of the comment!
@@ -20,55 +20,55 @@ func GetEnvOrDefault(envName string, defaultValue string) (output string) {
return output
}

// GetAppEnvFile ...
// GetAppEnvFile -
Copy link
Member

Choose a reason for hiding this comment

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

Why a hyphen?

Perhaps, if I put all of the comments on the same line this will not be needed?

Copy link
Author

Choose a reason for hiding this comment

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

oh, the hyphen was to offer a replacement character for the three dots, as i assumed you were using them for typographical/formatting reasons. They can be removed easy enough, but the three dots for whatever reasons marks the end of a go comment within go's tooling.

Copy link
Member

Choose a reason for hiding this comment

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

the three dots for whatever reasons marks the end of a go comment within go's tooling

I didn't know that! But that explains why in the LSP, it may not show the rest of the info about the comment!

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.

None yet

3 participants