Contexts/Data Sources Subsystem

Created on 22 August 2012, over 12 years ago
Updated 17 July 2023, almost 2 years ago

The plugin system has landed, and we need to revisit the Contexts/Data Sources plan. It looks like property api might have some non-trivial overlap in this regard, so that possibility should be explored.

What we need:

  1. Data Sources are essentially a metadata wrapping layer around various other data types to provide a consistent addressable wrapping layer for any type of data.
  2. This consistent wrapper should list what sort of data we are dealing with, as well as providing an extensible area for defining additional relevant metadata to the use case.

Implementation details

  1. CTools largely does what we need here already and likely the includes/context.inc file could be a strong guide for building an OOP centric solution for providing Data Sources.
  2. CTools utilizes a "context" plugin in order to accomplish its needs, it seem quite likely that the new plugin system in core could provide the same sort of support for this solution.
  3. In this solution the Plugin Definition would actually function as the data source's metadata, and we'd leverage plugin derivatives to support all the various solutions (For example, a single entity plugin could support all entity types and the Derivative class would replace the appropriate metadata with data relevant to the entity in question).

Eclipse

πŸ“Œ Task
Status

Postponed: needs info

Version

9.5

Component
OtherΒ  β†’

Last updated about 11 hours ago

Created by

πŸ‡ΊπŸ‡ΈUnited States eclipsegc

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Wonder if still valid request for D10?

  • Status changed to Closed: outdated 12 days ago
  • πŸ‡³πŸ‡ΏNew Zealand quietone

    There has been no work on this task for 12 years. It is likely that it is no longer needed or has been implemented. Therefor, closing.

    If there is work to do here, then either re-open the issue and add a comment or open a new issue and reference this one.

Production build 0.71.5 2024