Skip to content

how to handle arbitrary entities and attributes that don't fit in the spec? #57

Description

@pketh

Sort of connected to #55 , but if I have a document with other types of entities (like shapes I'm not sure whether adding those things as siblings to nodes and edges

{ 
  nodes: [],
  shapes: [{id, other attributes}]

would make a document non-compliant with the canvas spec , or whether canvas supporting apps would just ignore unsupported entities?

Relatedly, how should I handle custom attributes on nodes? If I make a node with a custom type like

{id: '123', type: 'list}

how would that node be handled in other canvas supporting apps? (In this case it would be fine if non-supported bits were ignored)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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