Closed (works as designed)
Project:
Drupal core
Version:
8.4.x-dev
Component:
aggregator.module
Priority:
Major
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Mar 2013 at 22:50 UTC
Updated:
18 May 2017 at 22:46 UTC
Jump to comment: Most recent
Comments
Comment #1
Crell commentedThat's the "deserializer" that we've been talking about in various places. The caveat is that the REST approach is more of a push model, where you'd message a site and say "here, have this node" rather than aggregator's pull-based model.
I don't know what it would take to make aggregator parse arbitrary feeds, or in this case to route a specific feed to the existing Serializer/Deserializer support. Aggregator already needs love to eliminate Drupal 3-era code: #1839468: [Followup] Replace aggregator rss parsing with Zend Feed
If someone is interested in working on this I can certainly try to point them in the right direction, although I think Lin Clark would be an even better resource.
Comment #2
berdirAggregator isn't that bad anymore, and we're working on making it better, see for example #1930274: Convert aggregator processors and parsers to plugins.
Zend Feed is a nice idea but not an option until the zend framework guys fix their dependencies (and possibly composer guys their dependency management) so that depending on zend feed doesn't include the complete zend framework, see the issue for details ;)
Comment #3
dawehnerMoving to 8.1.x
Comment #7
wim leersThis would require setting up a matching entity type (with a matching data model). Feeds have a very limited, predefined set of fields. That's a *huge* difference.