search

frmscoe / General-Issues

This repo exists to track current work and any issues within the FRMS CoE
2 stars 0 forks source link

Remove hard coded message type definition #325

Open cshezi opened 7 months ago

cshezi commented 7 months ago

Story statement

As a eKuta Developer, I want that typology processor to handle different types of messages, So that Typology processor can handle different messages even if within a single network map And so that Typology Processor is more generic based on message handling

Acceptance criteria

  1. Sending a different message should be possible
  2. Remove hard-coded type finding of a message
Justus-at-Tazama commented 2 months ago

Ref https://github.com/frmscoe/typology-processor/blob/dbfa844282d1e371a67503a3cca783fe2b3ec780/src/logic.service.ts#L178

The transactionType defines the format according to which the transaction message in the payload is composed. Transaction-specific information from the payload (e.g. msgId), or at least the transaction-specific location of the information, is used to key messages for logging and caching.