From 3f0255364526f199a68678797603b91e760360d0 Mon Sep 17 00:00:00 2001 From: Jeremy Vyska <35526546+JeremyVyska@users.noreply.github.com> Date: Fri, 6 May 2022 12:04:24 +0200 Subject: [PATCH] Update content/docs/patterns/template-method-pattern/index.md Co-authored-by: Henrik Helgesen --- content/docs/patterns/template-method-pattern/index.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/docs/patterns/template-method-pattern/index.md b/content/docs/patterns/template-method-pattern/index.md index 3f7df048..c8e5c3f7 100644 --- a/content/docs/patterns/template-method-pattern/index.md +++ b/content/docs/patterns/template-method-pattern/index.md @@ -147,9 +147,7 @@ codeunit 50002 ExportOrders Your code gains readability and it is very easy to add new cases for the template. You don't always have to think about the whole logic. You just have to implement the details ## When not to use -The Pattern should not be used for problems which differ to much. So for example if you have two data exports in your app, one is exporting header and lines and the second one only exports headers. In this case I would suggest to not use the pattern or to make two templates out of it. - - +The Pattern should not be used for problems which differ too much. For example, if you have two data exports in your app, one is exporting header and lines and the second one only export header. In this case I would suggest to not use the pattern or to make two templates out of it. ## References [Detailed Explanation of the pattern](https://patrickschiefer.com/2022/04/08/template-method-pattern/)