-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
package_api_docs
: fix or remove?
#57310
Comments
I guess you need $ dartanalyzer lib/*.dart --lints |
It seems that |
I'm hitting this now. As of 2.0.0-dev.39.0 |
What is |
`public_member_api_docs` is only supposed to warn for APIs that are
actually visible to the user – so not things in src (unless exported),
nothing in test, example, etc
…On Fri, Mar 16, 2018 at 10:30 PM Devon Carew ***@***.***> wrote:
What is package_api_docs supposed to do vs. public_member_api_docs?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#57310>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABCiuuBsAXHHmJZKqc-icLagtBBTGtiks5tfJ-DgaJpZM4H95dY>
.
|
Since we've overhauled the command line process for linting (maybe twice), I think this bug is stale. Please re-open if you hit this again. |
Is there any working example of this rule? I couldn't get any message for this rule. |
You're right. This lint is not working. Now that we have workspace support it could be fixed. Alternatively we should deprecate it and remove it. Sorry for the confusion! See also: #58385 |
I think this |
package_api_docs
is not working as expected
Re-opening so we can decide whether to fix or remove. Thanks for the nudge @leventkantaroglu! |
package_api_docs
is not working as expectedpackage_api_docs
: fix or remove?
Here's a simple package:
with
.analysis_options
:and
class.dart
:If I run the analyzer, I don't get any lint for the lack of documentation:
Based on the documentation, I would expect to get a message about
ThisIsATest
andreturnSomething
.The text was updated successfully, but these errors were encountered: