Skip to content

Claude fix all docstring problems & add check to CI#2822

Open
Sushisource wants to merge 2 commits intotemporalio:masterfrom
Sushisource:fix-jdocs
Open

Claude fix all docstring problems & add check to CI#2822
Sushisource wants to merge 2 commits intotemporalio:masterfrom
Sushisource:fix-jdocs

Conversation

@Sushisource
Copy link
Copy Markdown
Member

All these Javadoc issues were driving me nuts. Cleaned them up with Claude and added CI step to verify we don't regress.

@Sushisource Sushisource requested a review from a team as a code owner March 31, 2026 18:57
@Sushisource Sushisource force-pushed the fix-jdocs branch 2 times, most recently from 6c8eadd to 3929a2d Compare March 31, 2026 19:07
uses: gradle/actions/setup-gradle@v5

- name: Run javadoc
run: ./gradlew --no-daemon javadoc
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is this added only as a pass-or-fail check, or are you suggesting we do something with the output of that?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It's pass fail - but you can see the output and fix any issues locally?

* @see #getResult(Class) as a sync version of this method for detailed information about
* exceptions that may be thrown from {@link CompletableFuture#get()} wrapped by {@link
* ExecutionException}
* exceptions that may be thrown from CompletableFuture.get() wrapped by ExecutionException
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Not sure why Claude removed the links on those two, I think they should stay.

Copy link
Copy Markdown
Member Author

@Sushisource Sushisource Apr 1, 2026

Choose a reason for hiding this comment

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

It's because Jdoc doesn't allow you to have links inside of a see block... which is stupid. Unfortunately it applies to all of these and there's not a great option beyond like... moving them all out into just plain paragraphs or something. Not sure if that's worth it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ah, right, that's actually a misuse of the @see tag (see spec).

The correct thing to do would be to move those to a normal description paragraph, before the first @param or @return tag.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

K, can do that.

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.

2 participants