Transformer definition inconsistent #6

New issue

ruru4143 · 2023-10-05T15:55:38+02:00

ruru4143 commented

2023-10-05 15:55:38 +02:00

In our current document, we have (at least) 3 definitions of transformers:

A transformer as a one-to-one relation (kinda): ActivityPub object types-WordPress post types Matrix
A transformer as a one-to-many relation post to Note, Article, Image, Audio or Article depending on the post-format
A transformer as a many-to-one relation: Should a transformer be always a many-to-one relationship [...]
(only proposed): A transformer as a many-to-many relation: Should a transformer [...] be a many-to-many one

I don't see the advantage for many-to-x transformers, maybe somebody can give me a useful example. If not it would increase complexity in the user-interface and control flow of the plugin
I see the use of x-to-many transformers, not only in an multiple type way, rather than in an multiple types an objects way, see Castropod

some examples i want one transformer could be able to:

publishing one post(-type) in multiple objects at once (Castropod: Note and PodcastEpisode)
publishing one post(-type) in different shades of one object type (attachments)
publishing one post(-type) in different object types (notes and questions)
(?) reusing transformers in different transformers

In our current document, we have (at least) 3 definitions of transformers: 1. A transformer as a one-to-one relation (kinda): `ActivityPub object types-WordPress post types Matrix` 2. A transformer as a one-to-many relation `post to Note, Article, Image, Audio or Article depending on the post-format` 3. A transformer as a many-to-one relation: `Should a transformer be always a many-to-one relationship [...]` 4. (only proposed): A transformer as a many-to-many relation: `Should a transformer [...] be a many-to-many one` I don't see the advantage for many-to-x transformers, maybe somebody can give me a useful example. If not it would increase complexity in the user-interface and control flow of the plugin I see the use of x-to-many transformers, not only in an multiple type way, rather than in an multiple types an objects way, see Castropod some examples i want one transformer could be able to: * publishing one post(-type) in multiple objects at once (Castropod: Note and PodcastEpisode) * publishing one post(-type) in different shades of one object type (attachments) * publishing one post(-type) in different object types (notes and questions) * (?) reusing transformers in different transformers

ruru4143 commented

2023-10-05 15:58:00 +02:00

so i would propose a one-to-many transformer definition. which would also be easy to fit into a user-interface as it would only describe: this post-type should be handled by that transformer.

ruru4143 referenced this issue

2023-10-05 15:59:09 +02:00

Get the design documentation ready to hand over to the ActivityPub plugin maintainers for feedback. #5

linos commented

2023-10-05 16:04:52 +02:00

The current transformer already is a many-to-x one. It can transform all built-in and custom post types to a Note. And it has a template engine built-in. So that one can always just share the post title and the post link as a Note. If someone wishes to do that... I would consider it as a bad practice though...

The current transformer already is a many-to-x one. It can transform all built-in and custom post types to a `Note`. And it has a template engine built-in. So that one can always just share the post title and the post link as a `Note`. If someone wishes to do that... I would consider it as a bad practice though...

ruru4143 commented

2023-10-05 16:31:45 +02:00

should a transformer be able create two objects via one post? (see castropod)
should a transformer be able to transform one post_type into different object_types depending on the post-format?

1. should a transformer be able create two objects via one post? (see castropod) 2. should a transformer be able to transform one post_type into different object_types depending on the post-format?

linos commented

2023-10-05 17:02:42 +02:00

Note: technically the object type can be an array: https://www.w3.org/TR/activitystreams-core/#ex6-jsonld