- 🇯🇴Jordan Mutasim Al-Shoura
Reroll patch 14 from comment 19, against the latest version.
- 🇺🇸United States Fool2
Just a thought, what if we pulled in each channel item as entities and provided them to a view? Would it be too much overhead? Then sitebuilders could customize the import action completely and integrate it in many different ways.
Something like a "stub" entity or even an "Import status" entity for entities that haven't been imported yet.
Then the module could provide a default view (just like all the other views)
The stub could track uuid, remote, channel, title, and maybe last modification date on the remote. If we were to extend import status, we could also track the local relationship as well for imported entities. Then we provide the views plugins to access this entity and its relationships, we could rebuild the filters for the pull page as views filters.
This also has the opportunity to make the pull page asynchronous, so that the list of content has a manual "refresh" button where the stubs are imported via the remote channel feed(s)
This way, anyone could customize the UI by editing the view, they could create multiple UIs for different use cases, etc.