rails_event_store icon indicating copy to clipboard operation
rails_event_store copied to clipboard

Personalization of causation/correlation/type streams for browser

Open swistak35 opened this issue 6 years ago • 3 comments
trafficstars

Currently, displaying links (at browser) to correlation / causation / type streams work with assumption that our LinkBy* handlers are used with default prefix ($by_correlation_, $by_causation_, $by_type_) and with default metadata field (correlation_id, causation_id, event type).

There are two parts of this task:

  • ability to customize stream names in browser configuration ($by_correlation_, $by_causation_, $by_type_ mentioned above)
  • ability to customize the metadata fields used for that streams (correlation_id, causation_id)

IMO the first task is more important than the second.

swistak35 avatar Jun 25 '19 14:06 swistak35

Is this still an issue?

mostlyobvious avatar Dec 15 '20 01:12 mostlyobvious

The behavior mentioned above is still the case, and still confusing.

If you don't set up the LinkBy handlers as described in https://railseventstore.org/docs/v1/correlation_causation/#building-streams-based-on-correlation-id-and-causation-id those elements are still shown in the browser, but link to empty streams.

What I don't understand: why doesn't the ShowEvent view just show links to all streams that contain the event? That would be much more useful to me.

grncdr avatar Dec 23 '20 10:12 grncdr

What I don't understand: why doesn't the ShowEvent view just show links to all streams that contain the event? That would be much more useful to me.

Good question! There's already an API for that — streams_of(event_id). I have to remind myself if there were any performance implications.

mostlyobvious avatar Jan 05 '21 19:01 mostlyobvious

What I don't understand: why doesn't the ShowEvent view just show links to all streams that contain the event? That would be much more useful to me.

Scheduled for next release.

mostlyobvious avatar Sep 21 '22 21:09 mostlyobvious