patternfly / patternfly/patternfly-react
TableComposable: refactor Draggable example to use a data-driven rather than config-driven approach, and possibly new DragDrop abstraction
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 862
- Forks
- 392
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 9
Description
Followup from #6168. In converting that example to TypeScript + Hooks, I left its logic mostly unmodified because it's possible we will need to rewrite it to use the new DragDrop components anyway. Just opening this so we remember to follow up, because that example is left using a different paradigm than the others rewritten in #6168.
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 reviewing the Draggable example changes from #6168 and the current DragDrop components. Determine whether the example should move to a data-driven approach or use the new DragDrop abstraction; done means its approach is aligned with the other rewritten examples and the chosen direction is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100