Linked Properties not visible in the EdgeDB UI Data Explorer

[drewrawitz]

• EdgeDB Version: CLI 2.0.4+a7fc49b
• OS Version: macOS 12.0.1 (21A559)

Steps to Reproduce:

1. Add a linked property to your schema. Run your migration and then refresh the EdgeDB UI.
2. See that the linked properties are not shown anywhere.
3. Notice how you can still query for them in the REPL.

Schema:

  type Roster {
    required link team -> Team;
    required link player -> Player {
      property position -> FieldPosition;
      property number -> str;
    };
    required link season -> Season;
    required property isActive -> bool {
      default := true;
    };

    constraint exclusive on ((.team, .player, .season));
  }

EdgeDB UI:

REPL:

[izakfilmalter]

https://github.com/edgedb/edgedb-ui/issues/11

[Novark]

Just wondering if there's been any more discussion or progress on this feature.

Specifically, I was wondering if any thought has been given with regards to what the UI might look like to incorporate this. If the linked property is a complex type with many properties - how might these be displayed in a tabular view?

• Could this support multi linked properties in some sort of flattened / comma-separated list / chip-array?
• Would it be possible to have some sort of selection dialog that allows the user to select which properties they want displayed in the row to represent the linked object?
• Maybe it could default to using indexed properties as a means to represent the object as a whole?
• Could it facilitate deeply nested properties? So I could essentially reach multiple layers down in a linked object (even to nested links) and have a deeply nested property chosen as the value to display in the table view.

In my use cases, it's quite common for my types to have some form of identifying property that could be used to represent an object (table row) as a whole - often times it's a "name" or some sort of "display_text" property key.

Example:

In place of something like default::Player [7] appearing in the table cell (which currently links to a separate table view of the list of objects), it might show a flattened list of Player.name, so Bob, Alice, Carol [...] (which could still be clicked on, just as how it works now). If the horizontal space of the column is too small, you'd see ... to the right of the cell to indicate more entries that are not currently visible due to horizontal space constraints.

P.S. I'm brand new to EdgeDB, so apologies if any of my nomenclature is wrong or incorrectly used. I'm happy to clarify anything in this post if it's confusing. I'm still somewhat in that "trying-to-figure-out-how-to-describe-what-I'm-even-asking-for" phase. Hopefully this post was sufficiently descriptive.