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

Stranded vs unstranded in getReferenceRegions() for features #1513

Closed
devin-petersohn opened this issue May 3, 2017 · 1 comment
Closed

Stranded vs unstranded in getReferenceRegions() for features #1513

devin-petersohn opened this issue May 3, 2017 · 1 comment
Assignees
Milestone

Comments

@devin-petersohn
Copy link
Member

@devin-petersohn devin-petersohn commented May 3, 2017

Here we call ReferenceRegion.unstranded(), losing the strandedness information.

There are known issues using this in the joins when trying to join datatypes that have no stranded information from the start.

@fnothaft
Copy link
Member

@fnothaft fnothaft commented Mar 7, 2018

This appears to be out of date; I believe this is closed. We'll reopen if necessary later.

@fnothaft fnothaft closed this Mar 7, 2018
@heuermh heuermh added this to the 0.24.0 milestone Mar 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants