Re: ReSpec: linter
Shane McCarron <[email protected]> Thu, 14 Jul 2016 08:13:41 -0500
| Newsgroups | gmane.org.w3c.specifications |
|---|---|
| Message-ID | <CAJdbnOAFckoe4CmAdGDkO4dTR1-aRtdQbuX4PnXx=2E8L9T8eA@mail.gmail.com> |
--001a113ddc9c18d04c0537984784 Content-Type: text/plain; charset=UTF-8 BTW I have suggested we also add some a11y checking to this. I don't yet know what that will be. I am asking the APA and ARIA groups for input on it. But I wonder if there shouldn't also be a check for an a11y considerations section. I have raised an issue against specberus to discuss that with the relevant players. [1] Please feel free to comment here or against that issue. [1] https://github.com/w3c/specberus/issues/465 On Thu, Jul 14, 2016 at 8:06 AM, Wendy Seltzer <[email protected]> wrote: > On 07/14/2016 02:54 AM, Marcos Caceres wrote: > > Hi ReSpec Users, > +cc PING > > > > > As part of the W3C's transition to TLS docs on /TR/, we've added a > > simple linter to ReSpec to check that the URLs in your `respecConfig` > > are using TLS. > > > > The linter is disabled by default right now. You can enable it by > > adding the following to your `respecConfig`: > > > > ``` > > lint: true, > > ``` > > > > You can access the warnings through the ReSpec pill on the top-right, > > as per usual. If no warnings show up there, you are all good :) > > > > The linter also warns if you don't have a Privacy and/or Security > > Considerations section in your spec, with a helpful link to a > > questionnaire that can help you write such sections. > > Thanks Marcos, that's great! > > --Wendy > > > > > Once the W3C transitions to TLS on /TR/ (in ~2 weeks), we will enable > > the linter by default to help you easily fix such warnings. > > > > Kind regards, > > Marcos > > > > > -- > Wendy Seltzer -- [email protected] +1.617.715.4883 (office) > Policy Counsel and Domain Lead, World Wide Web Consortium (W3C) > https://wendy.seltzer.org/ +1.617.863.0613 (mobile) > > > -- Shane McCarron Projects Manager, Spec-Ops --001a113ddc9c18d04c0537984784 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">BTW I have suggested we also add some a11y checking to thi= s.=C2=A0 I don't yet know what that will be.=C2=A0 I am asking the APA = and ARIA groups for input on it.=C2=A0 But I wonder if there shouldn't = also be a check for an a11y considerations section.=C2=A0 I have raised an = issue against specberus to discuss that with the relevant players. [1] =C2= =A0Please feel free to comment here or against that issue.<div><br></div><d= iv><br></div><div><br></div><div>[1]=C2=A0<a href=3D"https://github.com/w3c= /specberus/issues/465">https://github.com/w3c/specberus/issues/465</a></div= ></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Ju= l 14, 2016 at 8:06 AM, Wendy Seltzer <span dir=3D"ltr"><<a href=3D"mailt= o:[email protected]" target=3D"_blank">[email protected]</a>></span> wrote:<= br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left= :1px #ccc solid;padding-left:1ex">On 07/14/2016 02:54 AM, Marcos Caceres wr= ote:<br> > Hi ReSpec Users,<br> +cc PING<br> <span class=3D""><br> ><br> > As part of the W3C's transition to TLS docs on /TR/, we've add= ed a<br> > simple linter to ReSpec to check that the URLs in your `respecConfig`<= br> > are using TLS.<br> ><br> > The linter is disabled by default right now. You can enable it by<br> > adding the following to your `respecConfig`:<br> ><br> > ```<br> > lint: true,<br> > ```<br> ><br> > You can access the warnings through the ReSpec pill on the top-right,<= br> > as per usual. If no warnings show up there, you are all good :)<br> ><br> > The linter also warns if you don't have a Privacy and/or Security<= br> > Considerations section in your spec, with a helpful link to a<br> > questionnaire that can help you write such sections.<br> <br> </span>Thanks Marcos, that's great!<br> <br> --Wendy<br> <div class=3D"HOEnZb"><div class=3D"h5"><br> ><br> > Once the W3C transitions to TLS on /TR/ (in ~2 weeks), we will enable<= br> > the linter by default to help you easily fix such warnings.<br> ><br> > Kind regards,<br> > Marcos<br> ><br> <br> <br> </div></div><span class=3D"HOEnZb"><font color=3D"#888888">--<br> Wendy Seltzer -- <a href=3D"mailto:[email protected]">[email protected]</a> <a = href=3D"tel:%2B1.617.715.4883" value=3D"+16177154883">+1.617.715.4883</a> (= office)<br> Policy Counsel and Domain Lead, World Wide Web Consortium (W3C)<br> <a href=3D"https://wendy.seltzer.org/" rel=3D"noreferrer" target=3D"_blank"= >https://wendy.seltzer.org/</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"tel:%= 2B1.617.863.0613" value=3D"+16178630613">+1.617.863.0613</a> (mobile)<br> <br> <br> </font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b= r><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div di= r=3D"ltr"><div><div dir=3D"ltr">Shane McCarron<div>Projects Manager, Spec-O= ps</div></div></div></div></div> </div> --001a113ddc9c18d04c0537984784--