WHAT DO YOU RECOMMEND?
I find myself wanting the following:
- Type inheritance – looks like it’s already been requested as in here: Multi-Type Vs. Inheritance
- Custom visualization of nested (linked) Objects in a Page. This also applies to the visualization of Gallery View “cards” for an Inline Query.
- Step 1: Define a Serializer that can select immediate properties and properties of potentially deeply nested Object properties. Akin to a Django DRF Serializer chain.
- Step2: Drag and drop those properties in a canvas view. The result is that I can capture a certain visualization of an Object to be embedded elsewhere.
HOW COULD IT BE DONE / REAL WORLD USE CASES?
I asked Claude to give me an example, this one works okay
:
Example Person: Sarah Chen
├── email: ``[email protected]
├── role: VP Engineering
├── company: → TechCorp (Object)
│ ├── name: TechCorp
│ ├── industry: SaaS
│ └── size: 500-1000
├── lastInteraction: → Meeting (Object)
│ ├── date: 2025-01-15
│ ├── type: Coffee Chat
│ └── nextSteps: Send proposal
└── projects: → [Project1, Project2] (Objects)
// User defines display template
{
“fields”: [
“name”,
“email”,
“role”,
“company.name”,
“company.industry”,
“lastInteraction.date”,
“lastInteraction.nextSteps”,
“projects[0:2].title” // First 2 projects
],
}
-
Let me use a canvas Block for the embedded (linked) Object to format the display, as in this sample Block or card:
┌────────────────────────────────────┐
│ Sarah Chen
│ VP Engineering
│ ──────────────────
│ 📧 ``[email protected]``
│ 🏢 TechCorp (SaaS)
│
│ Last Meeting: Jan 15, 2025
│ → Send proposal
│
│ Projects:
│ • AI Platform Migration
│ • Performance Optimization
└────────────────────────────────────┘
RECOMMENDED ALTERNATIVES
- If a complex Serializer feature isn’t possible: I’d like to, through a simplified interface, select properties of a Page’s linked Object and then drag those around a Block to format the display of the Object. I find that especially wanted for the Object’s display in the “card” of a Gallery View of an Inline Query.
ADDITIONAL CONTEXT
ᅟIf further context, people, or related Feature Requests should be mentioned, do so right here: