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

Validation service changed #76

Open
lawlesscreation opened this issue Jun 8, 2015 · 11 comments
Open

Validation service changed #76

lawlesscreation opened this issue Jun 8, 2015 · 11 comments

Comments

@lawlesscreation
Copy link

Looks like the W3C are throwing a new warning out when using their service:

1=> "This interface to HTML5 document checking is deprecated. Use the Nu Html Checker at https://validator.w3.org/nu/ directly instead." Line no: undefined
No of errors: 1

Might be a good idea to update the plugin to use https://validator.w3.org/nu/

@witrin
Copy link

witrin commented Jun 8, 2015

👍

1 similar comment
@danielmohacsi
Copy link

👍

@sideshowbarker
Copy link

Looks like the W3C are throwing a new warning out when using their service:

1=> "This interface to HTML5 document checking is deprecated. Use the Nu Html Checker at https://validator.w3.org/nu/ directly instead." Line no: undefined

Yeah, I just pushed that warning to the checker's XML-format output facet a few hours ago.

Might be a good idea to update the plugin to use https://validator.w3.org/nu/

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.

@retan
Copy link

retan commented Jun 8, 2015

It is a problem. It's driving me crazy for half a day.
Getting errors (with a loud beep) for no particular reason every time I change a few lines is not helping productivity.
Tumbs up for any, even temporary solution, ASAP pleas!!!

@embpdaniel
Copy link

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 :/

@lawlesscreation
Copy link
Author

It's not a long term solution, but you can add the error to relaxerrors:

relaxerror: [
            'This interface to HTML5 document checking is deprecated.'
        ]

Like I say, not a long term solution.

@embpdaniel
Copy link

@lawlesscreation Thank you, this will do the trick for now. It works :)

@retan
Copy link

retan commented Jun 9, 2015

@lawlesscreation Thank you.

basteln3rk pushed a commit to basteln3rk/bootstrap that referenced this issue Jun 17, 2015
- 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
@witrin
Copy link

witrin commented Jun 22, 2015

I've switched to grunt-html. With this plugin there is no need to be online and it uses the new validator.

@sideshowbarker
Copy link

I've switched to grunt-html. With this plugin there is no need to be online and it uses the new validator.

Aha. Actually I had misread the name of the repo this issue tracker is for. I had thought this actually was the grunt-html repo, which I already knew used the standalone vnu.jar release of the checker. So I had been wondering why emitting the new warning message was causing problems for the grunt-html. Now I understand that this issue is in a tracker for different repo, grunt-html-validator.

So I think the solution here for everybody is to for everybody who wants HTML checker integration with grunt to just use the grunt-html tool, which as far as I can is a superior solution to grunt-html-validator in pretty much every way. For one thing, given that is repo hasn't an substantive updates in a year, and there are no comments here in this issue from the grunt-html-validator maintainer @praveenvijayan.

jasny pushed a commit to jasny/bootstrap that referenced this issue Aug 7, 2015
- 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
@markusfalk
Copy link

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-*"]
      }
    }

jasny pushed a commit to jasny/bootstrap that referenced this issue Jan 3, 2016
- 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
azarakovskiy pushed a commit to RWS/dxa-html-design that referenced this issue Jul 6, 2017
… 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.
prodever added a commit to prodever/bootstrap that referenced this issue Jun 8, 2018
- 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
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

No branches or pull requests

7 participants