Currently when adding an item to your cart, it only updates the cart counter graphic for that browser instance, not all connected clients. Using SignalR it should be relatively straightforward to update the cart counter on all connected clients.

Adding links to guides like Node best practices or from RisingStack blog to README seems like a good way to recommend what works well with the app architecture.

In documentation about sagas there is this thing about storing saga-id into event metadata. It looks intuitive but it doesn't work out of the box :-(. I would like to make it work. Here is how:

1. from PublishAsync pass sagaId and saga type name into ICommandBus.PublishAsync()
2. overload ICommandBus.PublishAsync() so it takes an extra argument eventMetadata
3. pass event metadata to IAggregate

I figured out that node-sass dependency mentioned in web package is obsolete now.

I tried to change it to

"devDependencies": {
"@vue/cli-plugin-babel": "^3.0.0-rc.10",
"@vue/cli-plugin-eslint": "^3.0.0-rc.10",
"@vue/cli-service": "^3.0.0-rc.10",
"node-sass": "^4.14.0",
"sass-loader": "^7.0.3",
"vue-template-compiler": "^2.5.16"
},

then web-vue built s

In case there is a projection with no handlers we'd still traverse given streams only to produce no result. It's an unusual case but still we're able to produce "no result" much faster.

Can anyone give flow diagram which classes get hit in sequence from start to end in eventhorizon.
It will be great help I am waiting for this no documentation so far available on net.

What is this feature about?

At https://docs.wolkenkit.io/ we have the documentation for wolkenkit itself, but the APIs of the wolkenkit applications do not yet have any documentation. We could use the landing page of the broker to provide some automatically generated documentation based on the metadata of the model. This could help us to get closer to a self-documenting API.

What nee