You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2021/10/26 11:14:08 UTC

[GitHub] [flink] AHeise commented on pull request #17415: [hotfix][Path] Java doc redundancy and code style check clean-up

AHeise commented on pull request #17415:
URL: https://github.com/apache/flink/pull/17415#issuecomment-951831613


   Discussion on https://lists.apache.org/thread.html/rbf77ef3ccb28b03ed61c8c6eb344dba6e357cb8be4f3ec18e588c6ec%40%3Cdev.flink.apache.org%3E did not yield a clear result. I'd prefer to wait for Java 16 and use the mentioned `{@return}` in these cases.
   
   If you really want to clean up this JavaDoc pattern, it would be best to do it in all user-facing classes to keep it consistent as we usually value consistency the highest.
   
   For now, I'd close this PR. The larger effort probably deserves a Jira ticket.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org