Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / tc39/proposal-signals issues and pull requests
#259 - Focusing only on signals interoperability
Issue -
State: open - Opened by divdavem 13 days ago
- 3 comments
#258 - The signal graph protocol should be exposed for novel implementations
Issue -
State: open - Opened by DavidANeil 28 days ago
- 1 comment
#257 - Add utility for tracking Signal reads in a callback
Issue -
State: open - Opened by DavidANeil 28 days ago
#256 - Signals should be able to efficiently return to an old value
Issue -
State: open - Opened by DavidANeil 28 days ago
- 9 comments
#255 - Computed signals should expose a callback that is invoked when a value is dropped
Issue -
State: open - Opened by DavidANeil 28 days ago
#254 - Consumers can unexpectedly hold unused memory in dependencies
Issue -
State: open - Opened by DavidANeil 28 days ago
#253 - Allow Computeds to eagerly recalculate to prevent dirty propagation
Issue -
State: open - Opened by DavidANeil 28 days ago
#252 - Consumers should be held weakly to allow all nodes to be live
Issue -
State: open - Opened by DavidANeil 28 days ago
- 7 comments
#251 - `watcher.watch(signal)` and `Signal.subtle.watched` callback when signal is not up to date
Issue -
State: open - Opened by divdavem about 1 month ago
- 2 comments
#249 - `Signal.State.prototype.update` to update values using callbacks
Issue -
State: open - Opened by Ocean-OS about 2 months ago
- 4 comments
#248 - Fix use `Proxy` example code
Pull Request -
State: open - Opened by yusuke-omae about 2 months ago
#247 - Updates around this proposal
Issue -
State: open - Opened by WebReflection 3 months ago
- 7 comments
#246 - Signal should be replace with Reactive
Issue -
State: open - Opened by hansschenker 3 months ago
- 1 comment
#245 - Add note about globals
Pull Request -
State: open - Opened by NullVoxPopuli 3 months ago
#244 - React library that supports JavaScript Signals standard proposal
Issue -
State: open - Opened by finom 4 months ago
- 2 comments
#243 - Add `Signal.Buffer` alongside `Signal.State` and `Signal.Computed`
Issue -
State: open - Opened by dead-claudia 4 months ago
#242 - Rational: why no effects out of the box?
Issue -
State: open - Opened by NullVoxPopuli 5 months ago
- 3 comments
#241 - Subscription to a collection
Issue -
State: open - Opened by DanielHeath 5 months ago
- 2 comments
#240 - Fix typo
Pull Request -
State: open - Opened by samualtnorman 5 months ago
#239 - Add batching and batched effects to solve the interoperability / multi-actor problem with batches
Issue -
State: open - Opened by justinfagnani 6 months ago
- 2 comments
#238 - Better logo
Pull Request -
State: closed - Opened by littledan 6 months ago
#237 - Volatile sources in the computation graph
Issue -
State: open - Opened by PsychoLlama 6 months ago
- 7 comments
#236 - README.md: bug in Signal.subtle.Watcher.prototype.watch pseudocode
Pull Request -
State: closed - Opened by codefrau 6 months ago
#235 - Use `null` for `computing` rather than `undefined`
Pull Request -
State: closed - Opened by prophile 7 months ago
- 1 comment
#234 - Make clear that `Signal.State` has no state machine
Pull Request -
State: closed - Opened by prophile 7 months ago
#233 - Clarification request: (Semantic) equivalence of push-only and push/pull models
Issue -
State: open - Opened by dehmer 7 months ago
- 1 comment
#232 - Classes are useless here
Issue -
State: closed - Opened by Hadaward 8 months ago
- 5 comments
#231 - Drop the "recalculating" flag
Pull Request -
State: closed - Opened by prophile 8 months ago
#230 - Refactor Signal Class Hierarchy for Improved Type Safety and Extensibility
Issue -
State: open - Opened by DeepDoge 8 months ago
- 6 comments
#229 - Simpler logo
Pull Request -
State: closed - Opened by littledan 8 months ago
- 1 comment
#228 - Signals with Arguments
Issue -
State: closed - Opened by lishaduck 8 months ago
- 2 comments
#227 - Signal.subtle.watched/unwatched is not sufficient, we need to be notified when a signal is used (even without a watcher)
Issue -
State: open - Opened by divdavem 8 months ago
- 5 comments
#226 - How to allow `set` in a `Computed` to trigger a recomputation synchronously (until the result is stable)
Issue -
State: open - Opened by divdavem 9 months ago
- 7 comments
#225 - Who is this feature for?
Issue -
State: closed - Opened by baetheus 9 months ago
- 1 comment
#224 - Improves readability of code examples
Pull Request -
State: open - Opened by tomasbonco 9 months ago
#223 - Generalise the `notifying` semantics to `freezing`
Pull Request -
State: closed - Opened by prophile 9 months ago
#222 - Watcher simplification
Issue -
State: closed - Opened by dead-claudia 9 months ago
- 12 comments
#221 - Update README.md
Pull Request -
State: open - Opened by littledan 9 months ago
#220 - Do the benefits of signals as a language feature outweigh the costs of solidification into a standard?
Issue -
State: open - Opened by devmachiine 9 months ago
- 30 comments
#219 - cross realm signals
Issue -
State: open - Opened by mhofman 10 months ago
- 1 comment
#218 - Shorthand idea: `false` instead of `() => false` for `equals`
Issue -
State: open - Opened by NullVoxPopuli 10 months ago
- 5 comments
#217 - Explicitly spell out the state machines for `Computed` and `Watcher`
Pull Request -
State: closed - Opened by prophile 10 months ago
#216 - Polyfill bug: calling watcher.watch on computed signal (before its latest value is computed) can prevent from getting its correct latest value afterward
Issue -
State: closed - Opened by divdavem 10 months ago
- 2 comments
#215 - Really bad `unwatch` performance (3000%)
Issue -
State: open - Opened by lifeart 10 months ago
- 2 comments
#214 - Move polyfill to https://github.com/proposal-signals/signal-polyfill
Pull Request -
State: closed - Opened by NullVoxPopuli 10 months ago
#213 - Polyfill calls `equals` function unbound
Issue -
State: closed - Opened by prophile 10 months ago
- 2 comments
#212 - Polyfill example effect
Issue -
State: open - Opened by Phoscur 10 months ago
- 7 comments
#211 - Calling `.watch` inside a `Computed` callback
Issue -
State: closed - Opened by prophile 10 months ago
- 2 comments
#210 - Adding/removing watchers during execution of `set`
Issue -
State: closed - Opened by prophile 10 months ago
- 2 comments
#209 - Exceptions in `watched` callback leave `Watcher` in inconsistent state
Issue -
State: open - Opened by prophile 10 months ago
- 1 comment
#208 - Watchers have inconsistent state inside `watched` callback
Issue -
State: open - Opened by prophile 10 months ago
- 1 comment
#207 - Details omitted in `Watcher.getPending()`
Issue -
State: open - Opened by prophile 10 months ago
#206 - `watched` callback calling `.unwatch`
Issue -
State: closed - Opened by prophile 10 months ago
#205 - "Signal.subtle.Watcher.prototype.watch(...signals)" phase 4 is vague
Issue -
State: open - Opened by prophile 10 months ago
- 1 comment
#204 - "Watcher" state machine is undocumented
Issue -
State: closed - Opened by prophile 10 months ago
#203 - Spell out ordering of `sources`/`sinks` sets
Issue -
State: open - Opened by prophile 10 months ago
#202 - "Effect" is undefined in `Computed.get`
Issue -
State: open - Opened by prophile 10 months ago
- 2 comments
#201 - False positive in cycle detection for asymmetric cycles
Issue -
State: open - Opened by prophile 10 months ago
#200 - Question: `<template>` syntax
Issue -
State: closed - Opened by JosXa 10 months ago
- 3 comments
#199 - Cross-Scheduler Effect Cycle Detection
Issue -
State: closed - Opened by pjeby 10 months ago
- 1 comment
#198 - The end-goal should be to make framework compilers unnessecary
Issue -
State: open - Opened by cysabi 10 months ago
- 4 comments
#197 - Suggestion: don't recompute when dependent signals come back to previous values used for last computation
Pull Request -
State: open - Opened by divdavem 10 months ago
- 3 comments
#196 - Reasoning behind the push-then-pull model
Issue -
State: open - Opened by samholmes 10 months ago
- 15 comments
#195 - Have watchers track like computeds?
Issue -
State: open - Opened by dead-claudia 10 months ago
- 6 comments
#194 - Remove Angular-specific code
Pull Request -
State: open - Opened by dead-claudia 10 months ago
#193 - Remove `ngDevMode` condition on error message
Pull Request -
State: open - Opened by dead-claudia 10 months ago
- 1 comment
#192 - When a watcher for a computed depending on two sources is notified, if one source updates and a watcher is added during notification to the other source, an internal error is thrown
Issue -
State: open - Opened by dead-claudia 10 months ago
- 3 comments
#191 - [Polyfill] FIx - Deduplicate watched signals
Pull Request -
State: open - Opened by issammani 10 months ago
#190 - Support for incrementally computed signals, pursue history instead of dirty flags
Issue -
State: open - Opened by anglinb 10 months ago
- 2 comments
#189 - Add name to signal options
Issue -
State: closed - Opened by doeixd 10 months ago
- 1 comment
#188 - Proposal champions
Pull Request -
State: closed - Opened by littledan 10 months ago
#187 - Scopes
Issue -
State: open - Opened by doeixd 10 months ago
- 3 comments
#186 - Method to return cache status along with `.get()`
Issue -
State: closed - Opened by dead-claudia 10 months ago
- 4 comments
#185 - Add `Signal.subtle.requestSettledCallback`
Issue -
State: open - Opened by robbiespeed 10 months ago
- 14 comments
#184 - Synchronous effect w/out microtask?
Issue -
State: open - Opened by WebReflection 10 months ago
- 5 comments
#183 - chore: typo
Pull Request -
State: closed - Opened by posva 10 months ago
#182 - Rename `Signal.get` and `Signal.set` to `Signal.read` and `Signal.write`
Issue -
State: closed - Opened by titoBouzout 10 months ago
- 6 comments
#181 - [FER] change list, diff and previous values in Computed and watch
Issue -
State: open - Opened by yw662 10 months ago
- 1 comment
#180 - Make code in examples are clear and simple
Issue -
State: open - Opened by vitonsky 10 months ago
#179 - Way to temporarily exclude a watcher
Issue -
State: open - Opened by dead-claudia 10 months ago
- 5 comments
#178 - Let's start from the basics and work our way to what users need.
Issue -
State: open - Opened by dead-claudia 10 months ago
- 22 comments
#177 - Allow `state.set` during `Watcher(notify)`
Issue -
State: open - Opened by robbiespeed 10 months ago
- 2 comments
#176 - Add GC tests
Pull Request -
State: open - Opened by robbiespeed 10 months ago
- 1 comment
#172 - Use case for `Signal.subtle.{un,}watched` options for `Signal.Computed`?
Issue -
State: closed - Opened by dead-claudia 10 months ago
- 8 comments
#168 - Side APis to adapt
Issue -
State: open - Opened by y-nk 10 months ago
- 4 comments
#166 - Signal set seems unnecessary in the watcher?
Issue -
State: open - Opened by dead-claudia 11 months ago
- 11 comments
#164 - Should Signal.State / Signal.Computed have toJSON?
Issue -
State: closed - Opened by NullVoxPopuli 11 months ago
- 11 comments
#161 - Rationale: Autotracking
Issue -
State: open - Opened by NullVoxPopuli 11 months ago
- 19 comments
#159 - Pluggable "Graph Coloring"/"Graph Walking" Algorithm
Issue -
State: open - Opened by nathanhammond 11 months ago
- 7 comments
#156 - Watcher to accept WeakRef to allow watched live Signals to be Garbage Collected
Issue -
State: open - Opened by btakita 11 months ago
- 14 comments
#155 - A critical primitive: `Signal.Derived` (in addition to `Signal.Computed`) should be added.
Issue -
State: open - Opened by onurkerimov 11 months ago
- 2 comments
#152 - Can we use accessor instead of get/set methods?
Issue -
State: open - Opened by d8corp 11 months ago
- 5 comments
#151 - Uncached Computed?
Issue -
State: open - Opened by NullVoxPopuli 11 months ago
- 12 comments
#150 - Should `set` throw when called in `Signal.Computed` value callback?
Issue -
State: open - Opened by sorvell 11 months ago
- 4 comments
#149 - No effects outside of frameworks?
Issue -
State: open - Opened by wimbarelds 11 months ago
- 6 comments
#148 - Why the name "Signal"?
Issue -
State: open - Opened by realmazharhussain 11 months ago
- 13 comments
#147 - Core signal concerns (globals, auto/implicit tracking, async)
Issue -
State: open - Opened by TarVK 11 months ago
- 20 comments
#145 - Structured state based on signals
Issue -
State: open - Opened by unadlib 11 months ago
- 3 comments
#139 - Why are "watch" and "unwatch" hidden behind symbols?
Issue -
State: open - Opened by dead-claudia 11 months ago
- 8 comments
#137 - Should some EventTargets also be Signals?
Issue -
State: open - Opened by NotWoods 11 months ago
- 3 comments