OpenCloning / OpenCloning/OpenCloning_frontend
Multi-segment feature is duplicated when importing .dna file.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 10
- Avg merge
- 11d 9h
- Merged PRs (30d)
- 3
Description
I am using the Assembler and import a .dna file. The file contains a multi-segment feature. The
Here is what it looks like in Snapgene.
Here is what is looks like in Opencloning
I think the ideal outcome is to only have one feature with multiple segment. avrBs3 written in the glyphs and then the larger feature name (dTALE2) written above the glyph.
Note: I am not sure if this a frontend or a backend issue. Or actually an issue with pydna and I should be submitting this issue upsream? I am still wrapping my head around all these packages. Let me know if I should move the issue.
Also, for reference, here is the feature with all the details shown explicitly in the Snapgene feature editor.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the Assembler with the attached multi-segment .dna example, then trace the frontend's import flow to determine where the feature is duplicated. Compare the imported result with the Snapgene structure; done means one feature contains the multiple segments and the expected labels are displayed without duplication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100