Skip to content

added new rule: require-description-complete-sentence#109

Closed
dtracers wants to merge 17 commits intojscs-dev:masterfrom
dtracers:master
Closed

added new rule: require-description-complete-sentence#109
dtracers wants to merge 17 commits intojscs-dev:masterfrom
dtracers:master

Conversation

@dtracers
Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it can be reversed with return, what you think?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was actually going to do that but then I decided against it because I am adding a new test case for next line starting with an upper case letter.

If more cases are added someone might put another case after the return and then it may not run if it has nothing to do with the documentation ending with a period.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@qfox
Copy link
Copy Markdown
Member

qfox commented May 31, 2015

Nice work here ;-) Thanks!

What you think about this rules API? Should we document it? Is it comfortable for you?

@dtracers
Copy link
Copy Markdown
Contributor Author

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! 👍

This is a lot more specific now in terms of requirements.
@dtracers
Copy link
Copy Markdown
Contributor Author

Changed how the rules work so it will require another review.

Also build failed due to ssl error?

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.36%) to 95.77% when pulling b8e26d6 on dtracers:master into a34608a on jscs-dev:master.

@qfox
Copy link
Copy Markdown
Member

qfox commented Jun 9, 2015

Restarted job and it helps ;-\

I'll look into it tomorrow, thanks for you hard work here ;-)

@dtracers
Copy link
Copy Markdown
Contributor Author

dtracers commented Jun 9, 2015

Okay thank you!
On Jun 8, 2015 8:03 PM, "Alexej Yaroshevich" [email protected]
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
#109 (comment).

@qfox qfox closed this in 9e56f72 Jun 9, 2015
jdlrobson pushed a commit to jdlrobson/jscs-jsdoc that referenced this pull request Aug 21, 2015
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

Successfully merging this pull request may close these issues.

3 participants