Skip to content

Bug 2053531 - Add nimbus-fml lint - #7563

Open
travis79 wants to merge 1 commit into
mainfrom
Bug2053531
Open

Bug 2053531 - Add nimbus-fml lint#7563
travis79 wants to merge 1 commit into
mainfrom
Bug2053531

Conversation

@travis79

Copy link
Copy Markdown
Member

Adds a lint command covering feature metadata, descriptions, naming and feature design, and a no-lint field to silence lints per feature or per file. validate no longer reports feature metadata warnings; that's the lint command's job now.

Pull Request checklist

  • Breaking changes: This PR follows our breaking change policy
    • This PR follows the breaking change policy:
      • This PR has no breaking API changes, or
      • There are corresponding PRs for our consumer applications that resolve the breaking changes and have been approved
  • Quality: This PR builds and tests run cleanly
    • Note:
      • For changes that need extra cross-platform testing, consider adding [ci full] to the PR title.
      • If this pull request includes a breaking change, consider cutting a new release after merging.
  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Changelog: This PR includes a changelog entry in CHANGELOG.md or an explanation of why it does not need one
    • Any breaking changes to Swift or Kotlin binding APIs are noted explicitly
  • Dependencies: This PR follows our dependency management guidelines
    • Any new dependencies are accompanied by a summary of the due diligence applied in selecting them.

Adds a lint command covering feature metadata, descriptions, naming and
feature design, and a `no-lint` field to silence lints per feature or per
file. `validate` no longer reports feature metadata warnings; that's the
lint command's job now.
Comment on lines +341 to +345
let mut raw = Vec::new();
metadata::check_feature(feature, &mut raw);
documentation::check_feature(feature, &mut raw);
naming::check_feature(feature, &mut raw);
design::check_feature(feature, fm, &mut raw);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Adding these feels like something that could get missed when adding new linting files. Could it be at all viable to instead have the methods be on a trait? Then have the trait get impl'd on structs for each lint type, and have each section iterate through the types and call the appropriate methods?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants