Closed dtracers closed 9 years ago
Nice work here ;-) Thanks!
What you think about this rules API? Should we document it? Is it comfortable for you?
For what I was doing it was pretty easy because I just copied an existing rule from an existing pull request.
If I had not done that I would have been pretty lost. But I did not actually go and look for documentation of it. I copied off of https://github.com/jscs-dev/jscs-jsdoc/pull/99/files.
I think in your documentation for making rules you should actually choose a pull request that shows all the parts needed for a rule.
I would actually use this one: https://github.com/jscs-dev/jscs-jsdoc/pull/98/files
And then in this one pull request add extensive documentation of what each part means. Explain what the tags mean and how they look in a jsdoc. Explain the scoping and the different options. Add documentation explaining what node, tag, and err is.
And I feel that would make it easier than just a bunch of text. But that is just me! :+1:
Changed how the rules work so it will require another review.
Also build failed due to ssl error?
Restarted job and it helps ;-\
I'll look into it tomorrow, thanks for you hard work here ;-)
Okay thank you! On Jun 8, 2015 8:03 PM, "Alexej Yaroshevich" notifications@github.com wrote:
Restarted job and it helps ;-\
I'll look into it tomorrow, thanks for you hard work here ;-)
— Reply to this email directly or view it on GitHub https://github.com/jscs-dev/jscs-jsdoc/pull/109#issuecomment-110197452.
Added a new rule that requires the description to be a complete sentence.
A complete sentence starts with an upper case letter and ends with a period