-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Meta] Add javadocs #221
Comments
Excludes modules currently failing from missingJavadoc check. These modules can be removed from exclusion list once javadocs are added. Currently, only :client:rest module is enabled for missingJavadoc check. Issue opensearch-project#221 tracks javadocs for legacy code. These checks are enabled as part of gradle check. Enabling it as part of precommit needs more work and will be done later. Once this PR is merged all incoming PRs will undergo javadoc validations. Signed-off-by: Himanshu Setia <[email protected]>
Excludes modules currently failing from missingJavadoc check. These modules can be removed from exclusion list once javadocs are added. Currently, only :client:rest module is enabled for missingJavadoc check. Issue #221 tracks javadocs for legacy code. These checks are enabled as part of gradle check. Enabling it as part of precommit needs more work and will be done later. Once this PR is merged all incoming PRs will undergo javadoc validations. Signed-off-by: Himanshu Setia <[email protected]>
Hi @setiah, do you have plan to add missing javadocs for this list of modules? how to track the progress? |
Hey @anasalkouz adding javadocs for all modules is a behemoth effort which we need to divide and conquer with the help from community. Evaluating other priorities, we need to bring this in our sprint planning and conquer module-by-module and parallelize where possible. For some modules like |
Given that we have a number of plugins extending internal class functionality that shouldn't be extended, I am going to start pushing progress toward enabling the This will also include two new javadoc annotations ( NOTE: THIS SHOULD NOT ACT AS A SUBSTITUTE FOR USING GOOD CLASS/METHOD MODIFIERS (e.g., |
@nknize how should we take this forward so that respective teams can pick up and we make progress on this meta issue? |
Should we "javadocument" testcase or ignore them for now ? |
@ker2x I would skip tests. |
Signed-off-by: Vacha Shah <[email protected]> Signed-off-by: Vacha Shah <[email protected]>
Description
This is a meta issue to track javadoc progress for all modules that are currently missing javadocs. Once javadocs are added, we can enable
missingJavadoc
task as part of gradle checks, to enable strict javadoc validation.How to reproduce
<Needs update once #721 is merged>
main
branch)and switch to remote(Note:javadoc
branchjavadoc
branch is deprecated now)./gradlew missingJavadoc
javadoc-output.txt
file for failures due to missing javadocsLogs
Subtasks
Currently most modules are failing javadoc validations due to missing javadocs.
How to help
Please add javadocs for the module you work on. Validate the module using the missingJavadoc gradle task.
For example, if you are adding javadocs for
:client:rest
module, you can validate your changes using command./gradlew :client:rest:missingJavadoc
command.The text was updated successfully, but these errors were encountered: