npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

eventstore-ts-projection-builder

v1.0.18

Published

A helper for building eventstore projection with typescript

Downloads

27

Readme

Eventstore : typescript projection builder

The aim of this lib is to give a helper for building eventstore projections using the strength of ts.

This lib is based on this official documentation page

How to build a projection

A first example will be very explicit :

export const buildRoomAvailabilityProjection = (): string => {
  const projectionBuilder: ProjectionBuilder = new ProjectionBuilder();
  const bookedRoomsState: BookedRoomsState = new BookedRoomsState();

  return projectionBuilder
    .addSelector(
      new FromStreamsSelector(['manager.room-added', 'guest.room-booked']),
    )
    .addFilter(
      new WhenFilter([
        new InitHandler(bookedRoomsState),
        new EventTypeHandler('RoomAddedEvent', roomAddedEventHandlerCallBack),
        new EventTypeHandler('RoomBookedEvent', roomBookedEventHandlerCallBack),
      ]),
    )
    .addFilter(new OutputStateFilter())
    .exportProjection();
};

As you can see on this peace of code, you just have to declare a builder method. This method will use a ProjectionBuilder object that will aggregate all projection elements you need.

The result of buildRoomAvailabilityProjection() will be the projection as string, ready to be upserted into eventstore. The code produced corresponds to the typescript callbacks compiled in js and cleaned with prettier. So it's highly readable, and easy to debug in the eventstore interface if needed.

Assuming that you already know how to build a projection, and what is a selector, a filter etc (yet based on the doc), here is the list of each projection element available in this lib :

The list of selectors :

FromAllSelector
FromCategorySelector
FromStreamSelector
FromStreamsSelector

The list of filters :

FilterByFilter
ForEachStreamFilter
OutputStateFilter
PartitionByFilter
TransformByFilter
WhenFilter

The handlers :

InitHandler
InitSharedHandler
EventTypeHandler
DeletedTypeHandler
AnyHandler

The options properties :

export interface ProjectionOptionsModel {
  resultStreamName?: string;
  $includeLinks?: boolean;
  processingLag?: number;
  reorderEvents?: boolean;
}

You can add linkTo or emit method into your callbacks by using the given ones of the lib.

The main advantage of this way to do is that you can type your callbacks and test it easily. For example in the example given, the state, the events and the callbacks are fully typed, and you can add the structures you want. That makes the projection highly maintainable. This example is volontary a bit complex, to show that this lib allows to use custom structures thanks to typescript, that would have been hard to use in pure js because of absence of types.

A full and very trivial example of projection :

export class CheckInState {
  guests: string[] = [];
}

export const guestRegisteredEventCallBack = (
  state: CheckInState,
  event: RegisteredEvent,
): void => {
  for (let i = 0; i < state.guests.length; i++) {
    if (state.guests[i] === event.data.clientName) {
      return;
    }
  }
  state.guests.push(event.data.clientName);
  emit('myStream', 'myEventType', event.data, event.metadata)
};

export const buildRegisteredGuestsProjection = (): string => {
  const projectionBuilder: ProjectionBuilder = new ProjectionBuilder();
  const checkInStateState: CheckInState = new CheckInState();

  return projectionBuilder
    .addSelector(new FromStreamsSelector(['guest.registered']))
    .addFilter(
      new WhenFilter([
        new InitHandler(checkInStateState),
        new EventTypeHandler('RegisteredEvent', guestRegisteredEventCallBack),
      ]),
    )
    .addFilter(new OutputStateFilter())
    .exportProjection();
};

This will produce a projection string like this :

fromStreams("guest.registered")
  .when({
    $init: function () {
      return { guests: [] };
    },
    RegisteredEvent: function (state, event) {
      for (var i = 0; i < state.guests.length; i++) {
        if (state.guests[i] === event.data.clientName) {
          return;
        }
      }
      state.guests.push(event.data.clientName);
      emit('myStream', 'myEventType', event.data, event.metadata)
    },
  })
  .outputState();