Skip to content

Project graphs should have layers #8

Description

@breadchris

A project graph should provide an end-to-end visualization of a project, encompassing all the different elements and their interconnections. This visualization should account for various layers of complexity to accommodate projects with diverse components.

In these projects, it's crucial to differentiate between various types of nodes and connections, representing them individually for clarity.

Take a standard workflow as an example. It comprises resources and nodes, with the potential for resources to depend on other resources. The dependencies or connections between these resources and nodes should be explicitly definable within the project graph.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions