Skip to content

v3: Redesign Data hierarchy #7556

Description

@edan-bainglass

Following up on a comment made in #7138, we here consider the following restructure:

  1. There is only Data
  2. Sub-types no longer extend Data directly
  3. Data is still unique by node_type per data type (in DB)
  4. Sub-types implement (and register via entry-point system):
    i. Utility interface, accessible via Data.value
    ii. Pydantic schemas
  5. If sub-type package is not installed:
    i. Data.value raises dedicated message (with instructions)
    ii. Pydantic schema is not accessible, leading to attributes remaining a simple dict

@giovannipizzi

Metadata

Metadata

Labels

Type

No type

Fields

Priority

Urgent

Projects

Status
No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions