From 30dd7618bf1aa50d5ea96e23ba9041639382c6a6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Menrath?= Date: Tue, 10 Oct 2023 15:59:41 +0200 Subject: [PATCH] transofmer: current state : make relations more clear --- architecture design proposal.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/architecture design proposal.md b/architecture design proposal.md index 6667c70..c1d48c1 100755 --- a/architecture design proposal.md +++ b/architecture design proposal.md @@ -75,12 +75,15 @@ Nevertheless, we see a lot of other cases that can benefit, if the primary goals ## User Interface ### Current situation + +#### Frontend The admin user interface in v1.0.0 lets one choose to which object type all post get transformed to. The options are: * [x] Note (default) — Should work with most platforms. * [ ] Article — The presentation of the "Article" might change on different platforms. * [ ] WordPress Post-Format — Maps the WordPress Post-Format to the ActivityPub Object Type. -Currently, only one hard-coded transformer exists in `includes/transformer/class post.php` ([Source](https://github.com/Automattic/wordpress-activitypub/blob/master/includes/transformer/class-post.php)). +#### Backend +Currently, all this functionality is handled via one hard-coded transformer in `includes/transformer/class post.php` ([Source](https://github.com/Automattic/wordpress-activitypub/blob/master/includes/transformer/class-post.php)) and the actual logic that assigns the type is somewhere else. ```php /**