Optimize the system design of the Transformer_Base class #3
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Event-Federation/wordpress-activitypub#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Transformer_Base class is atm just a basic copy of the upstream Post Transformer class.
The
to_object
functino does pretty much everything. Most stuff it does is pretty common and new transformers probably just want to copy that functionality.But other transformers also might want to add new object keys. Like location and place. And with each new key there also may come a new context that must be delivered due to json-ld.
We have to think about future implications carefully and maybe rethink how this is done at the moment.
I also wonder what might become reusable in the future...
I will close this issue, cause what it covers until now is directly related to #1.