-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat!: update tx segment element with updated cool-seq-tool structure changes #314
Merged
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
fa8c93c
feat!: update tx segment element with updated cool-seq-tool structure…
katiestahl 9a6281d
fix: tx segment element bugs
katiestahl fbe0a83
update response models
katiestahl b2c6787
feat: update variable names with cool-seq-tool updates
katiestahl 053843e
feat: update calls to fusor and cool-seq-tool with updated params
katiestahl f314306
Merge branch 'staging' into cool-seq-tool-tx-updates
katiestahl b58a5b7
update fusor version
katiestahl 726d7e6
updating fusor version
katiestahl 6c672bd
wip: fixing tests from cool-seq-tool and fusor updates
katiestahl d56bff0
tests: updating tests with fusor changes
katiestahl 7191723
fixing test examples and adding checks for correct start/end on seque…
katiestahl 09e10bd
update reqs
korikuzma 7f56752
fix: bug where chromosome field was not editable
katiestahl f26dd9f
Merge branch 'cool-seq-tool-tx-updates' of https://github.com/cancerv…
katiestahl a8833e4
removing editable field for now since it's not working as designed, w…
katiestahl c3d093c
changing validation for tx segment elemetn since they only require ei…
katiestahl b611f84
refactor: remove ability to change strand, since it's auto populated
katiestahl e5545eb
removing strand switch
katiestahl 09183e1
fix: ability to change strand for templated sequence
katiestahl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
please double check me on this change! From my understanding, based on the sequence location changes, a Tx segment element only requires either a start/end, regardless of position (it looks like previously, it had to have both unless it was the first item?)
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.
Yes only one of start/end is required to create a TranscriptSegmentElement