Problem/Motivation
It would be useful to display scheduled action data in [node-based] views, and exposing this data to Views in a basic form should be fairly simple.
Proposed resolution
Implement hook_views_data() to describe some scheduled actions data to Views and relate it to nodes. This could later be extended to any relevant entity type.
Remaining tasks
Review/test.
User interface changes
Users of Views UI for node views will now have the option to add fields pertaining to scheduled actions targeting nodes in that view (fields including scheduled action time, triggered time, and action ID/name/type), as well as filter and sort by those fields.
API changes
Users of Views API will have access to these new fields.
Comments
Comment #1
ndewhurstHere's a patch that provides the described functionality. I split it between scheduled_actions and scheduled_actions_node to be more modular (envisioning other modules following suit, e.g. "scheduled_actions_user" implementing hook_views_data_alter() and relating users to scheduled actions). Does that seem good? The modulename.views.inc files are sitting in module roots with no special path, but this could obviously be organized differently if desired.
Comment #2
ndewhurstComment #4
slashrsm commentedGreat work! Committed. Thanks!