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

Add doc links throughout our user-facing APIs #1239

Merged

Conversation

tdeebswihart
Copy link
Contributor

What was changed

I backfilled doc links throughout our user-facing APIs. I didn't touch the internal package as those aren't supposed to be for external consumption.

While here I cleaned up a few things, like adding links to referenced code samples and removing a doc comment in a spot where they're unsupported; you can't add links in the comments on interface methods or struct members.

Why?

Linking readers to referenced APIs saves them time when trying to understand how to use temporal.

Checklist

This was tested by running godoc locally and inspecting the rendered docs. Note that cross-package doc links still don't work so cannot be verified locally.

@tdeebswihart tdeebswihart requested a review from a team as a code owner September 15, 2023 21:11
@tdeebswihart tdeebswihart force-pushed the add-links-to-godoc branch 2 times, most recently from 4443bee to 281efbb Compare September 15, 2023 22:11
Copy link
Member

@cretz cretz left a comment

Choose a reason for hiding this comment

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

Nice, thanks!

@cretz
Copy link
Member

cretz commented Sep 18, 2023

I didn't touch the internal package as those aren't supposed to be for external consumption.

Not necessarily true (many times that's the only way we can document struct fields). But this LGTM, feel free to merge at will or let us know if it won't let you.

@tdeebswihart
Copy link
Contributor Author

I didn't touch the internal package as those aren't supposed to be for external consumption.

Not necessarily true (many times that's the only way we can document struct fields). But this LGTM, feel free to merge at will or let us know if it won't let you.

Yeah, I'm used to those being internal only so skipped them out of habit. If missing docs still bothers me I'll take a swing at those too

Backfill doc links throughout our user-facing APIs. I didn't touch the
internal package as those aren't supposed to be for external
consumption.

While here I cleaned up a few things, like adding links to referenced
code samples and removing a doc comment in a spot where they're
unsupported; you can't add links in the comments on interface methods or
struct members.
@Quinn-With-Two-Ns Quinn-With-Two-Ns merged commit 22435a7 into temporalio:master Sep 18, 2023
6 checks passed
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