-
Notifications
You must be signed in to change notification settings - Fork 50
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
Warn on duplicate fields #229
Comments
Duplicate Edit: On closer inspection, it turns out that this warning is located in dead code. |
This message is probably a leftover debug message. In any case, it is not very informational to the user. It might be useful to warn on duplicate fields for fields where there is no need to include them multiple times, but that should be done in a more consistent way. For example, documenting the same parameter more than once could also be warned about. I created twisted#229 as reminder.
This is a partial implementation of twisted#229: ideally we'd want to warn on duplicate `type` and `keyword` fields as well, but for `type` this is currently not easy to implement and `keyword` isn't used enough to make it a priority.
This is a partial implementation of twisted#229: ideally we'd want to warn on duplicate `type` and `keyword` fields as well, but for `type` this is currently not easy to implement and `keyword` isn't used enough to make it a priority.
#296 implements a warning for duplicate It would be good to have a warning for duplicate The same |
If for example a return value or a parameter is documented more than once, it would be useful to warn the user about that.
Note that fields such as
author
,note
andseealso
can be used multiple times, so not all duplicate fields are a problem.The text was updated successfully, but these errors were encountered: