OpenAPITools / OpenAPITools/openapi-generator
[Java][QUESTION] Placeholder JavaDoc 'deprecated' description?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Whenever generating DTOs in Java, the generated JavaDocs will include @deprecated when it's marked as deprecated, like so:
/**
* Example of a deprecated Enum
*
* @deprecated
*/
@Deprecated
public enum DeprecatedExampleEnum {
However, it will result in compilation warnings:
[EmptyBlockTag] A block tag (@param, @return, @throws, @deprecated) has an empty description. Block tags without descriptions don't add much value for future readers of the code; consider removing the tag entirely or adding a description. (see https://google.github.io/styleguide/javaguide.html#s7.1.3-javadoc-block-tags)
Question
Should there be some placeholder value? Unless... is there some vendor-extension to provide the deprecation details?
Simply adding a dot will resolve the warnings. Or perhaps "details missing". Thoughts?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the generated JavaDoc example and the EmptyBlockTag warning described in the issue. Determine whether deprecation details are available from the OpenAPI input or a vendor extension, then clarify the expected placeholder or metadata behavior. Done means the decision is documented and generated Java DTOs no longer produce the reported warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100