-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Remove useless and empty Javadoc #659
Comments
Yes agreed. I feel like this is a problem that hasn't always existed. Let's definitely sort this out for the next version. I'm not interested in adding a config property for this, the javadoc just shouldn't be added if there is no useful information. |
It looks like the empty javadoc has been introduced for all fields by #645. |
The |
@joelittlejohn I fully agree. Thanks. |
@annawinkler Hopefully this link will help: http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html |
That helped - thanks!
Anna
…On Fri, Mar 3, 2017 at 5:15 PM, Joe Littlejohn ***@***.***> wrote:
@annawinkler <https://github.com/annawinkler> Hopefully this link will
help: http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-
javadoc.html
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#659 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADXPezEfsi_9o3yip5uJpOA22Grj5kZdks5riK0NgaJpZM4LJL1C>
.
|
Hi
The generated javadoc is useless if no description is provided in the json schema.
Additionally an empty javadoc appears on properties which doesnt make sense.
For such cases the javadoc generation should be disabled.
Aditionally a toggle could be added for the javadoc generation.
The text was updated successfully, but these errors were encountered: