Adapt incomplete-signature-doc to warn about incomplete, not missing docs #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndreaWalchshoferSCCH
changed the title
AlWoSp
requested changes
Jun 28, 2023
AlWoSp
approved these changes
Jun 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the diagnostic
incomplete-signature-docis ignoring fully undocumented functions - but is already triggered by a simple comment.This turns out to be impractical in a few cases, as it also forces a full documentation of functions that should just be annotated with
---@async(and is therefore not yet fully compatible withawait-in-sync)So this PR adapts the diagnostic to only warn about incomplete signature docs, so it requires at least one
@paramor@returnannotation before a warning is given. (Otherwise, it would be a missing signature doc, and there's separate diagnostics about that...)