From bd2448d9505ed7cdb75909def022f7306e03cdf5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Menrath?= Date: Tue, 10 Oct 2023 16:01:52 +0200 Subject: [PATCH] change importance of transformer backend solution points --- architecture design proposal.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/architecture design proposal.md b/architecture design proposal.md index 4233628..86ecfac 100755 --- a/architecture design proposal.md +++ b/architecture design proposal.md @@ -147,9 +147,9 @@ Use WordPress's hook system or a public API function to let other plugins regist **Possible alternatives and solutions:** - The ActivityPub plugin could provide reusable Traits for common tasks. -- Highly unlikely: The ActivityPub plugin provides an even more height level framework for adding transformers. For example for events the ActivityPub plugin could provide a built-in transformer to the object type `Event` which only needs a mapping (might make things harder, instead of making them easier). See Appendix. -- Don't use an interface with implementations, (miss)use class extensions. - Provide useful functions, documentation, and examples for automatic testing of transformers. +- Highly unlikely: The ActivityPub plugin provides an even more height level framework for adding transformers. For example for events the ActivityPub plugin could provide a built-in transformer to the object type `Event` which only needs a mapping (might make things harder, instead of making them easier). See Appendix. +- Highly unlikely: don't use an interface with implementations, (miss)use class extensions. # Mapping: Actors and Dispatching