From a22a667b32ecee47f570adfe9cae9c5f5486ce71 Mon Sep 17 00:00:00 2001 From: Sander Dijkhuis Date: Tue, 15 Oct 2019 18:17:02 +0200 Subject: [PATCH] docs: document RuntimeEvent access removal in v3 Based on an explanation by @Tim-Linschoten: https://github.com/ing-bank/baker/issues/287#issuecomment-542261760 --- docs/sections/versions/baker-3-release-notes.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/sections/versions/baker-3-release-notes.md b/docs/sections/versions/baker-3-release-notes.md index 7c597bac6..13d93a7e2 100644 --- a/docs/sections/versions/baker-3-release-notes.md +++ b/docs/sections/versions/baker-3-release-notes.md @@ -221,4 +221,12 @@ In this release we have removed sieves completely. In JBaker we supported using a UUID as a processId. In this release this has been removed completely and we accept Strings. This is again in line with being clearer what Baker does. -Internally we were just transforming this to a String. \ No newline at end of file +Internally we were just transforming this to a String. + +### Accesss to RuntimeEvents +Version 2 would provided undocumented public interfaces returning RuntimeEvent instances. +In version 3, the possibility to get Ingredients provided by a specific Event is gone. +Users should not care where ingredients are provided from. +This could be from an SensoryEvent or as output of a Event from an Interaction. +This should not matter, only if the ingredient is available should matter. +This allow users to flexibly recipes without impacting client code.