OpenCloning / OpenCloning/OpenCloning_frontend
Minimal usability requirements
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 10
- Avg merge
- 11d 9h
- Merged PRs (30d)
- 3
Description
I think for real world usage these two things are really needed:
- Being able to annotate sequences
- Allow assembly to cut through features rather than deleting them.
- Alignments between sequences in the session
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
No files, tests, or entry points are identified. Start by surveying the frontend's sequence annotation, assembly, and alignment features, then clarify the expected behavior and acceptance criteria for each requested capability before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100