Project:Feed Element Mapper
Version:6.x-2.x-dev
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Ideally we could use FEMP for mapping not only to node-based feed items, but any feed items.

Once #397682: Let mappers declare mapping targets lands, we are a lot closer to independency from nodes, because detection of mapping targets will not be the responsibility of feedapi_mapper.module anymore.

What's missing then is wrapping the node object in a mapping target object:

// Simple mapper target object wrapper.
class feedapiMapperTarget {
  public $type; // e. g. 'node'
  public $object; // e. g. $node object
}

and modifying the mapping code accordingly. For instance, node mappers would not react to mapping objects that aren't of type node, RDF mappers would not react to mapping targets of type RDF.

Comments

#1

Title:Make mapper node independent» Make mapper node-independent

#2

Assigned to:Anonymous» alex_b

Taking a shot at this now.

#3

Assigned to:alex_b» Anonymous
Status:active» needs review

This patch passes all tests. Working on a none-node implementation using this patch now.

Ready for review.

AttachmentSize
433384-3_feedapi_node_independent.patch 16.98 KB

#4

Update to reflect recent commits.

AttachmentSize
433384-4_feedapi_node_independent.patch 17.04 KB

#5

- Fix admin/content/node-type forms.
- Updated api.php

I suggest committing this to a new branch DRUPAL-2 as we're changing the API slightly and there are more fundamental changes to come.

AttachmentSize
433384-5_feedapi_node_independent.patch 18.82 KB

#6

Version:6.x-1.x-dev» 6.x-2.x-dev
Status:needs review» fixed

Committed to 2.x.

#7

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.