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.

Sign up for GitHub

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

Jump to bottom

add tag to suppress Vale errors/warnings for specific case #52

Closed
FedorRomanov opened this issue Dec 12, 2017 · 3 comments
Closed

add tag to suppress Vale errors/warnings for specific case #52

FedorRomanov opened this issue Dec 12, 2017 · 3 comments
Labels
Status: Resolved

Comments

@FedorRomanov
Copy link

Some errors/warnings reported by Vale are perfectly valid English prose. Ultimately, Vale just provides suggestions, potential issues and only author should decide if text needs corrections of not.
It would be very handy to have an ability to suppress such specific 'style smells' by using special tag, e.g.

<!DOCTYPE html>
<html>
<p>In many cases, ......be returned.<!--novale.begin-->Note that<!--novale.end--> the geocoder is very tolerant...
</html>

When processing the such tag vale should not report an issue:

1:426   warning  Consider removing 'Note that'  vale.Editorializing

Similar tags could be added for other file formats(Java, C, PHP, e.t.c.)
@jdkato
Copy link
Member

jdkato commented Dec 27, 2017

This is currently available in Markdown, HTML, and reStructuredText (see https://valelint.github.io/docs/config/#using-comments).

@jdkato jdkato closed this as completed Aug 8, 2018
@refaelsh
Copy link

This is currently available in Markdown, HTML, and reStructuredText (see https://valelint.github.io/docs/config/#using-comments).

The link does not works. I was googling exactly this issue, but the link does not works.

@andrewferrier
Copy link

It appears that the documentation has moved here: https://vale.sh/docs/topics/config#markup-based-configuration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Resolved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@andrewferrier @refaelsh @FedorRomanov @jdkato