-
Notifications
You must be signed in to change notification settings - Fork 244
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
Move bad coordinates check #911
Conversation
@yfarjoun Please review. |
Codecov Report
@@ Coverage Diff @@
## master #911 +/- ##
===============================================
+ Coverage 65.084% 65.091% +0.007%
- Complexity 7265 7268 +3
===============================================
Files 528 528
Lines 31948 31946 -2
Branches 5455 5453 -2
===============================================
+ Hits 20793 20794 +1
Misses 9011 9011
+ Partials 2144 2141 -3
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comment about spaces. also, could you put an issue that parseReg doesn't work for sequences that have colons or dashes in their names?
@ronlevine are you still available to process this? if not @lbergelson what's the procedure? |
@cmnbroad can you take over this? |
@yfarjoun Sure. |
@yfarjoun I don't see anything in this PR that addresses the second issue raised in the ticket. A couple of questions: Do you think we should we retain the current behavior where querying a non-existent sequence name silently returns an empty iterator ? It seems to me it should throw. Same for start index <= 0. Such queries seem incoherent, but the caller has no way to notify the user. It would be a behavior change though. |
iter=tabixReader.query("1",Integer.MAX_VALUE,-1); | ||
Assert.assertNotNull(iter); | ||
Assert.assertNull(iter.next()); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a test case in which end == 0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also add test cases for the other overloads of query()
, since they have difference interval conventions (the String version is 1-based closed, the 3-arg version is 0-based closed-open!)
Review complete, back to @cmnbroad |
ping.... |
@yfarjoun I'm taking this over, but don't have the ability to assign since I don't have commit privileges. |
assigned to you @fleharty |
@droazen Back to you. |
0244ade
to
c50da95
Compare
@yfarjoun my court |
820362a
to
0e4e15a
Compare
Codecov Report
@@ Coverage Diff @@
## master #911 +/- ##
==============================================
+ Coverage 69.5% 69.517% +0.016%
- Complexity 8399 8403 +4
==============================================
Files 558 558
Lines 33371 33369 -2
Branches 5610 5608 -2
==============================================
+ Hits 23193 23197 +4
+ Misses 7904 7901 -3
+ Partials 2274 2271 -3
|
looks good now. |
Description
Follow up to #908.
Move the bad coordinates check to the root method,
public Iterator query(final String reg)
. If this public method is used by an application, the bad coordinates will return anEOF_ITERATOR;
Checklist