We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
@internal
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
Consider:
class A { @internal int field = 0; }
In this scenario, A.field will be visible in Dartdoc's generated website. But that's obviously undesired
A.field
We can also add /// @nodocs, but that feels a bit redundant. I think it'd be more logical if a @internal implied /// @nodoc
/// @nodocs
/// @nodoc
The text was updated successfully, but these errors were encountered:
Duplicate of #2418
Sorry, something went wrong.
No branches or pull requests
Consider:
In this scenario,
A.field
will be visible in Dartdoc's generated website. But that's obviously undesiredWe can also add
/// @nodocs
, but that feels a bit redundant. I think it'd be more logical if a@internal
implied/// @nodoc
The text was updated successfully, but these errors were encountered: