Requesting a position on the Observable API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api, documentation
Research direction
Read issue #72 and the linked WICG/observable proposal first, then review the discussion about the boundary between Observables and Signals. Done means documenting a WinterCG position or decision on whether the Observable API belongs in the minimum common API.
Written by the indexing model from the issue text.
Description
Hi there, at the Web Engines Hackfest I raised the question of how to get a WinterCG "position" about new web API proposals. Along with others, @littledan mentioned that for now, filing issues against this repository will do.
I'd like to get Winter's position on the Observable API, as proposed in https://github.com/WICG/observable. Observables are a long-awaited and highly desired ergonomic improvement for event handling.
I'll admit I'd still like to do my research on where exactly the line should be drawn between Observables and Signals in terms of their usage (at the moment I know almost nothing about Signals except for what some people described to me in person). But still it would be good to get a gut check on this proposal by experts over here, sooner than later. Thanks!
- Dominant language
- Bikeshed
- Stars
- 308
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
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.
More from WinterTC55/proposal-minimum-common-api
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WinterTC55/proposal-minimum-common-api#117 · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WinterTC55/proposal-minimum-common-api#107 · 4 reactions ·
-
2026 edition roadmap Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
WinterTC55/proposal-minimum-common-api#106 · 2 reactions ·
-
Serialization? Open
Difficulty 5/5 Over a week Newbie friendliness 18/100
WinterTC55/proposal-minimum-common-api#99 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in WinterTC55/proposal-minimum-common-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·