Skip to content
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

Validate part directive for libs with parts #576

Conversation

corwinsheahan-wf
Copy link
Contributor

Fixes #522

Motivation

The boiler plate validation logic doesn't currently account or the case where the component declarations are in a part of file.

Changes

  • When analyzing a file which is a self-contained lib, run boilerplate validation and part directive validation.
  • When the file is a part of, just run the boilerplate validation, but not any part directive validation.
  • When we are in a parent lib file, examine the contents of all files in a lib and validate the part directive if any files in the lib contain over_react declarations.

Release Notes

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

  • Tests were updated and provide good coverage of the changeset and other affected code
  • Manual testing was performed if needed

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

  • A Client Platform member has reviewed these changes
  • There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
  • For release PRs - Version metadata in Rosie comment is correct

@aviary2-wf
Copy link

Security Insights

No security relevant content was detected by automated scans.

Action Items

  • Review PR for security impact; comment "security review required" if needed or unsure
  • Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

… into link-2020/validate_generated_part_for_parent
@@ -67,6 +87,8 @@ class BoilerplateValidatorDiagnostic extends DiagnosticContributor {
// Do not lint anything that is not a likely boilerplate member that will actually get generated.
if (member.versionConfidences.toList().every((vcp) => vcp.confidence <= Confidence.neutral)) continue;

if (isPart(result.unit)) continue;
Copy link
Contributor

Choose a reason for hiding this comment

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

Because of this, there's no error if components are declared in parts and there's no generated import in the main library.

Sorry, I can't remember; we going to handle that case in a separate PR?

Copy link
Contributor

Choose a reason for hiding this comment

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

For posterity: we'll handle this separately

@greglittlefield-wf
Copy link
Contributor

QA +1

Copy link
Contributor

@aaronlademann-wf aaronlademann-wf left a comment

Choose a reason for hiding this comment

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

+1

@@ -238,3 +229,11 @@ extension<E> on Iterable<E> {
});
}
}

// TODO use the version from over_react instead after initial release
Copy link
Contributor

Choose a reason for hiding this comment

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

Added #585 to address this TODO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants