Fix for regex sequence search on reverse strand features #4366
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue raised in the gitter chat about reverse strand sequence searches failing. The start and end coordinates were not correctly calculated, leading to inconsistencies across blocks and thus broken features. This fixes it by using the match.length instead of the search.length, and fixing how that was applied to (a) coordinates to doesIntersect2, (b) the feature coordinates, (c) the feature id.