Skip to content
This repository was archived by the owner on Apr 17, 2020. It is now read-only.
This repository was archived by the owner on Apr 17, 2020. It is now read-only.

contextualizations/contextualizers : switch to a multi-resources model #3

@robindemourat

Description

@robindemourat

Right now the contextualizers api allows to consume only one resource to produce a contextualization. It should be changed to allow more complex contextualizers and thus be future-proof.

Change in contextualizations generic model :

Actual :

{
  // ...
  "resource": {
    "type": "string"
  }
}

Future (alternative 1) :

{
  // ...
  "resources": { // list of resources of id
    "type": "array",
    "items": {
      "type": "string"
    }
  }
}

Future (alternative 2)

{
  // ...
  "resources": { // hashmap of keys/values, in which keys correspond to roles in the contextualizer, and values to resources' uuid
    "type": "object"
  }
}

Repercussions :

  • contextualizers APIs
  • templates contextualization wrappers components
  • editors design

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions