From 15c06bd0b27033228f58ae4691e68077668c49e0 Mon Sep 17 00:00:00 2001 From: waldo1001 Date: Thu, 10 Feb 2022 17:01:08 +0100 Subject: [PATCH] cleanup --- content/BCPatterns/event-bridge-pattern/index.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/BCPatterns/event-bridge-pattern/index.md b/content/BCPatterns/event-bridge-pattern/index.md index 0d210e4b..69ccb946 100644 --- a/content/BCPatterns/event-bridge-pattern/index.md +++ b/content/BCPatterns/event-bridge-pattern/index.md @@ -29,12 +29,11 @@ interface "IScale" Multiple apps can subscribe to certain events of the app. When a new implementation is created, we need to make sure that these events are raised at the right times. If those events were published on the implementation codeunit, it might very well be that those events will not be raised, hard to find, or whatever. -So, if we would implement it like this, it isn't really extensible, as a different implemention would impement different events .. and it's not possible to subscribe to all of them (inculding future implementations) +So, if we would implement it like this, it isn't really extensible, as a different implemention would implement different events .. and it's not possible to subscribe to all of them (including future implementations) ```AL codeunit 50407 "Scale Wrong" implements IScale { - procedure GetWeight() Result: Decimal; begin //TODO: Implement Bar GetWeight @@ -63,7 +62,7 @@ codeunit 50407 "Scale Wrong" implements IScale To mitigate this problem, we can work with a new, dedicated, isolated, codeunit, with publish events to be able to raise them from different places. -``` +```AL codeunit 50406 "IScale Triggers" { [IntegrationEvent(false, false)] @@ -108,7 +107,7 @@ The naming convention (both starting with "IScale") also makes it very easy to f ## When not to use -Obiously, the events should be carefully considered: only the events that make sense to "share" over all implementations, need this approach. +Obviously, the events should be carefully considered: only the events that make sense to "share" over all implementations, need this approach. ## Discussions