learningequality / learningequality/studio
Legacy clipboard nodes cause considerable code complexity needs mitigation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Summary
To handle clipboard nodes created in production Studio, the frontend clipboard logic has two separate data flows to deal with new and old clipboard nodes.
It may be better to simply write a data migration task to handle these old clipboard nodes (whether in the frontend or the backend) to resolve this and only have to maintain one smaller set of data logic in future.
Contributor guide
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 tracing the frontend clipboard logic and how legacy clipboard nodes created in production Studio are represented. Determine whether the migration belongs in the frontend or backend, then define the migration scope and verify that the separate old-node and new-node data flows can be replaced by one maintained flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100