Dealing with useEffects in WorkflowDiagram
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Description
useEffects in WorkflowDiagram are quite tricky to deal with. let's take a deeper look at them once again. we might be able to consolidate some of them and get rid of others.
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 locating the WorkflowDiagram entry point and reviewing all of its useEffects. Determine which effects can be consolidated or removed, then verify that the diagram still behaves correctly after the refactor; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, react
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100