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

feat(linter): introduce raw ast rules #239

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

araujogui
Copy link
Member

Description

Validation

Related Issues

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I've covered new added functionality with unit tests if necessary.

issues.push(...rule(entries));
issues.push(...rule(ast));
Copy link
Member

@avivkeller avivkeller Mar 28, 2025

Choose a reason for hiding this comment

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

WDYT about there being be a way for the linter to accept entries OR ast, depending on what it needs. For some scenarios, getting the AST may be preferable

Whatever you think is best

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't have a strong opinion about this, I can make a simple test so we can decide what is the best option.

@araujogui
Copy link
Member Author

I refactored the invalid-change-version to an initial version that uses mdast and yaml ast to correctly report line numbers. Feedback is welcome @nodejs/web-infra

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.

3 participants