You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment all the processing is done in a single step: Raw Event -> Call a mapping function. We can design a more robust processing system, roughly working as follows:
Transform as defined in the mapping (with type-safe parameters)
The processing steps should be fully open-ended and implement a common interface. In particular, it should be possible to import a public pipelining step as a self-contained npm library and simply include it in the manifest file.
The text was updated successfully, but these errors were encountered:
This is a follow-up issue on #61
At the moment all the processing is done in a single step: Raw Event -> Call a mapping function. We can design a more robust processing system, roughly working as follows:
The processing steps should be fully open-ended and implement a common interface. In particular, it should be possible to import a public pipelining step as a self-contained npm library and simply include it in the manifest file.
The text was updated successfully, but these errors were encountered: