<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">If possible, I’d really prefer we left linting work to Newton. It’ll be good to get it to a more usable state again, but we ought to be focusing on thoroughly checking the new Launch Instance for bugs and edge usage cases, as well as the outstanding
bugs and blueprints targeted at RC1 (<a href="https://launchpad.net/horizon/+milestone/mitaka-rc1" class="">https://launchpad.net/horizon/+milestone/mitaka-rc1</a>). This is a great opportunity to prove that the Angular rewrites are fully capable of providing
an improved experience, and we should be capitalising on that.</div>
<div class=""><br class="">
</div>
<div class="">Rob</div>
<div class=""><br class="">
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 9 Mar 2016, at 02:25, Richard Jones <<a href="mailto:r1chardj0n3s@gmail.com" class="">r1chardj0n3s@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Hey all,
<div class=""><br class="">
</div>
<div class="">I started looking into fixing the wall of "npm run lint" warnings today and quickly noticed that about 85% of the "linting" warnings were about jsdoc. We have significant issues around jsdoc anyway and we're supposed to be using Sphinx anyway[1].</div>
<div class=""><br class="">
</div>
<div class="">Some Horizon folks will know that I've been investigating generating publishable documentation for our Javascript code for some time. Most of the tools either don't work (dgeni) or produce pretty unusable output for a project our size (jsdoc and
grunt-ngdocs). I am about to investigate Sphinx in collaboration with the docs team.</div>
<div class=""><br class="">
</div>
<div class="">Regardless, I believe that the documentation generation should generate errors about that documentation, not the code linter. Once we actually get a documentation generator going. Until then, we don't even know what syntax the documentation should
follow.</div>
<div class=""><br class="">
</div>
<div class="">I've proposed a change which just turns jsdoc "linting" off[2]. At the moment, it is less than useful (the noise drowns out any other, legitimate linting).</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""> Richard</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">[1] <a href="http://governance.openstack.org/reference/cti/javascript-cti.html" class="">http://governance.openstack.org/reference/cti/javascript-cti.html</a></div>
<div class="">[2] <a href="https://review.openstack.org/#/c/290235/" class="">https://review.openstack.org/#/c/290235/</a></div>
<div class=""><br class="">
</div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</body>
</html>