Skip to content

fix: isNew in imports does return correct value #8

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Jul 15, 2017
Merged

fix: isNew in imports does return correct value #8

merged 3 commits into from
Jul 15, 2017

Conversation

buehler
Copy link
Owner

@buehler buehler commented Jul 15, 2017

No description provided.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.4%) to 81.272% when pulling 9d3cf8d on fix/is-new-on-imports into 06fc66a on develop.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+1.4%) to 81.272% when pulling 9d3cf8d on fix/is-new-on-imports into 06fc66a on develop.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.4%) to 81.272% when pulling 9d3cf8d on fix/is-new-on-imports into 06fc66a on develop.

@buehler buehler merged commit 3cc7822 into develop Jul 15, 2017
@buehler buehler deleted the fix/is-new-on-imports branch July 15, 2017 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@buehler @coveralls