WICG / WICG/declarative-partial-updates
Extend Considered Alternatives with example code
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 13
- Avg merge
- 12m
- Merged PRs (30d)
- 3
Description
It would be helpful in weighing up this design to see how the various approaches listed in the considered alternatives section work in practice. Not having sample code to compare to makes it difficult to understand why this design is superior.
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 locating the design document's “Considered Alternatives” section and review the approaches listed there. Add representative example code for those alternatives so readers can compare them with the proposed design; the section should clearly explain why the proposed design is preferable.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100