pnp / pnp/sp-dev-fx-controls-react
class hierarchy in controls
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 433
- Forks
- 418
- Avg merge
- 5d 6m
- Merged PRs (30d)
- 19
Description
shouldn't we have some kind of class hierarchy in these controls? at a minimum, controls used to render list fields should have a common base class.
also, would be good to design the interface separately from the library so we could more easily move away from fabric if needed.
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
Review the existing React control implementations to understand how list-field controls currently relate; the issue names no files or tests. Compare their interfaces and rendering-library dependencies, then define completion as a documented hierarchy and interface boundary that addresses both requested design concerns.
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