Skip to content

Conversation

@mpbarano
Copy link

Description

This change adds documentation to 4 @lucene.internal classes in the geo package.

This is my first contribution to Lucene. I have read the CONTRIBUTING.md. This change is part of #15225. This change started with Cursor LLM, but I have read everything. I have tried my best to validate that the information is accurate. And I altered the language to remove unnecessary adverbs or other awkward language.

The provided docs are verbose, but they seem useful. I would be happy to have feedback about whether the amount of content is appropriate or whether they should be more terse.

@github-actions
Copy link
Contributor

This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop receiving this reminder on future updates to the PR.

@dweiss
Copy link
Contributor

dweiss commented Oct 24, 2025

I agree these docs are... verbose. I keep wondering if it makes sense to add llm-generated documentation back to the project - seems like we'd be feeding the snake with its own tail if there's something wrong in there. :) This seems ok though.

Copy link
Contributor

@jainankitk jainankitk left a comment

Choose a reason for hiding this comment

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

Looks fine to me. Although, I am wondering if we really need verbose documentation for classes annotated @lucene.internal. But, I guess it shouldn't hurt!

@jainankitk jainankitk added this to the 10.4.0 milestone Oct 24, 2025
@jainankitk
Copy link
Contributor

Okay, I was wondering why the github workflow did not automatically add milestone even though CHANGES entry is present. It seems to be added in the 10.3.0 section. @mpbarano - Can you move the CHANGES entry to 10.4.0 section?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants