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

Preventing NaN in printed annotations #485

Merged
merged 1 commit into from
May 17, 2016

Conversation

honzajavorek
Copy link
Contributor

@honzajavorek honzajavorek commented May 16, 2016

Preventing

(warning code 1) expected API name, e.g. '# <API Name>' on lines NaN-NaN, lines NaN-NaN

@honzajavorek
Copy link
Contributor Author

honzajavorek commented May 16, 2016

The coverage dropped (-0.002%), but actually probably just because the overall percentage of lines has changed. I'm not going to add any tests, there's nothing left to cover in parts of the code I touched. Most of my PR are actually added tests 😐

@freaz freaz self-assigned this May 17, 2016
@@ -58,4 +58,9 @@ blueprintUtils.rangesToLinesText = (ranges) ->
return pos


module.exports = blueprintUtils
Copy link
Contributor

Choose a reason for hiding this comment

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

To think about: The original approach is imo better because it allows you to stub/spy functions inside module.

@freaz freaz merged commit e842526 into master May 17, 2016
@honzajavorek honzajavorek deleted the honzajavorek/prevent-nan-in-annotations branch May 17, 2016 12:08
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.

None yet

2 participants