@nanostores/query exposes async state as:
while @nanostores/async uses a state-machine shape.
This makes it difficult to use query stores with computedAsync directly.
Example:
const $post = createFetcherStore<Post>(['/api/post/', id]);
const $derived = computedAsync($post, post => {
return doSomething(post);
});
Question
Is there any plan to align these APIs or provide an official adapter?
Related discussion:
nanostores/async#2
@nanostores/queryexposes async state as:while
@nanostores/asyncuses a state-machine shape.This makes it difficult to use query stores with
computedAsyncdirectly.Example:
Question
Is there any plan to align these APIs or provide an official adapter?
Related discussion:
nanostores/async#2