Skip to content
This repository was archived by the owner on Nov 20, 2024. It is now read-only.

fix public_member_api_docs overreporting on effectively private constructors #4535

Merged
merged 1 commit into from
Jul 5, 2023

Conversation

pq
Copy link
Contributor

@pq pq commented Jul 5, 2023

@coveralls
Copy link

Coverage Status

coverage: 96.759% (+0.002%) from 96.757% when pulling b574ab0 on public_member_api_docs_sealedCons into 73e243b on main.

!isPrivate(node.name) &&
node.parent is! EnumDeclaration) {
check(node);
if (inPrivateMember(node) || isPrivate(node.name)) return;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code duplication with an earlier PR concerns me. I'm wondering whether we want to add the lines below to inPrivateMember (or add a new utility method to include the overall semantics), maybe making it an extension method in the process.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. I've got another PR in the wings for @internal. I'll address this duplication there. Thanks!

@pq pq merged commit 02d83f0 into main Jul 5, 2023
@pq pq deleted the public_member_api_docs_sealedCons branch July 5, 2023 18:45
copybara-service bot pushed a commit to dart-lang/sdk that referenced this pull request Aug 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

public_member_api_docs: constructors on sealed classes are not really public
3 participants