-
Notifications
You must be signed in to change notification settings - Fork 39
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
Validation service changed #76
Comments
👍 |
1 similar comment
👍 |
Yeah, I just pushed that warning to the checker's XML-format output facet a few hours ago.
Yup. If there's any problem with the warning that's creating issues for users I could revert it temporarily. But it's there for a reason. |
It is a problem. It's driving me crazy for half a day. |
This error is keeping my project from building. I tried changing the 'serverUrl' option to https://validator.w3.org/nu/ but then I get a network error. Am I supposed to use this url to remove the error, or is there something else I need to do? heeelp :/ |
It's not a long term solution, but you can add the error to relaxerrors:
Like I say, not a long term solution. |
@lawlesscreation Thank you, this will do the trick for now. It works :) |
@lawlesscreation Thank you. |
- deprecation notice of w3 service causes build to fail (upstream issue: praveenvijayan/grunt-html-validation#76) - should ampersand be escaped in url parameters? opinions differ; current practice in docs is not to escape URL parameter ampersands, and this need not cause the build to fail
I've switched to |
Aha. Actually I had misread the name of the repo this issue tracker is for. I had thought this actually was the So I think the solution here for everybody is to for everybody who wants HTML checker integration with grunt to just use the |
- deprecation notice of w3 service causes build to fail (upstream issue: praveenvijayan/grunt-html-validation#76) - should ampersand be escaped in url parameters? opinions differ; current practice in docs is not to escape URL parameter ampersands, and this need not cause the build to fail
I tried the relaxerror option or using a different URL but in any combination I get a network error. I suspect a timeout? large files? any idea? validation: {
options: {
reportpath: false,
reset: true,
serverURL: 'https://validator.w3.org/nu/',
relaxerror: [
'This interface to HTML5 document checking is deprecated.'
]
},
files: {
src: ["build/**/*.html", "!build/**/ajax-*"]
}
} |
- deprecation notice of w3 service causes build to fail (upstream issue: praveenvijayan/grunt-html-validation#76) - should ampersand be escaped in url parameters? opinions differ; current practice in docs is not to escape URL parameter ampersands, and this need not cause the build to fail
… instructed by praveenvijayan/grunt-html-validation#76 should use the https://validator.w3.org/nu/ instead but that doesn't work correct, so we might need to change to a different html validator for Grunt.
- deprecation notice of w3 service causes build to fail (upstream issue: praveenvijayan/grunt-html-validation#76) - should ampersand be escaped in url parameters? opinions differ; current practice in docs is not to escape URL parameter ampersands, and this need not cause the build to fail
Looks like the W3C are throwing a new warning out when using their service:
Might be a good idea to update the plugin to use https://validator.w3.org/nu/
The text was updated successfully, but these errors were encountered: