Thanks. I think it makes sense to split the connect into components / svelte as discussed in slack and a peer dependency feels right for people whoaren't using svelte.

I'd still like to work with svelte more before adding this to rdx though - the connect layer is pretty small but I want to validate the patterns a bit more first. For instance, instead of doing the connect in each component, it seems to work well to just create and import a connected 'state' and also use that to access the dispatch methods as well (which is why I originally added it instead of it just returning the subscribe method).

🤔
Indeed themapState +mapEvents combo leans towards the "classical" React / Redux integration heritage. While I have not done a lot of coding with Svelte yet, I do agree it does not really match the reactive (forward referencing) nature of Svelte. Maybe a single module like this would be more "svelte-ish"? Something like that, maybe:

// src/state/state-store.tsimport{connect}from'@captaincodeman/rdx/svelte'import{store}from'./store'exportconststateStore=connect(store)

And then use it like this:

<!-- src/ui/Foo.svelte --><scriptlang="ts">import{stateStore}from'../state/state-store'import{fooSelectors}from'../state/models/foo'  $:numberOfFoos=fooSelectors.fooCount($stateStore)</script><h1>There {numberOfFoos === 1 ? 'is' : 'are'} {numberOfFoos} {numberOfFoos === 1 ? 'foo' : 'foosens'}</h1><buttonon:click={stateStore.dispatch.foo.addFoo()}>Add a foo</button>

The one thing I really dislike about the snippets I just wrote is, that both Rdx and Svelte use the term "store" and it means something different. That does feel like an invitation for misunderstandings (and difficult to write or very wordy docs).

Then, again, if it wasexport const state = ..., then the client code would readstate.dispatch.foo.addFoo(), while for a class based (web component based) UI it would bestore.dispatch.foo.addFoo(). I do not like that one timedispatch is on the (Rdx) store, and once it's on some intermediary which might be mistaken forstore.state (wherestore is the Rdx store). I think, after all, I'd prefer, to just importdispatch fromsrc/state/store.ts, as seems to be idiomatic for Rdx (per the docs).

So, to sum it up: Maybe best just to provide read access to the Rdx store's state through a custom Svelte store, and havedispatch exported as it is fromsrc/state/store.ts (i.e. limit the amount of "magic")?