-
Notifications
You must be signed in to change notification settings - Fork 64
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
basic linting behind --lint-spec #199
Conversation
Statement[${M}a]: \`;\` | ||
</emu-grammar> | ||
`, | ||
"Parameter 'a' is unused." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these messages being passed through from Grammarkdown's built-in linting? I don't like how its capitalisation and quoting are inconsistent with ours. And I prefer that ours does not change because it's better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alas, they are.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we prefix grammarkdown messages or somehow indicate they came from grammarkdown?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ehhh, that doesn't seem like a distinction users are likely to care about.
This implements several of the ideas in #173, and hopefully provides a scaffolding which allows contributing more lint rules relatively easily.
Depends on tc39/ecmarkdown#69 being released; marked as a draft until then.Edit: done, ecmarkdown 5.0.1 is released and used in this PR.