Add rule to check the usage of charset meta tag #199
Conversation
| const isHTMLDocument = (targetURL: string, responseHeaders: object) => { | ||
|
|
||
| // If it's a local file, just presume it's a HTML document. | ||
| // TODO: Change this! |
There was a problem hiding this comment.
@molant When working with local files, rules will need a way to know what type of file they are dealing with.
(and I think this will became more important in the "text editor scenario")
| Sending just the `Content-Type` HTTP header is in general ok, but it's | ||
| usually a good idea to also add the charset meta tag because: | ||
|
|
||
| * Server configurations might change (or servers might not send the |
There was a problem hiding this comment.
There is a trailing space in this line. The tests are failing because of this hehehe
|
@alrra I think this is one of those rules that should check the browserlist for some of it. As you say in the documentation, modern browsers alias |
My opinion is that we should stick to
|
|
@molant Updated the docs. |
Fix #81