Uh oh!
There was an error while loading. Please reload this page.
feat(app-shell): auto-derive gantt + map bindings for interface pages - #1811
Merged
Conversation
Interface pages already auto-derive kanban / calendar / gallery / timeline field bindings from the object when those visualizations are whitelisted. Extend the same treatment to the last two record visualizations so a list/interface page can offer ANY visualization by whitelisting it alone — no hand-wiring: - `defaultGanttFromObject` — picks a start + end date field (name-disambiguated start/end/due, else the first two date fields) + an optional progress field. - `defaultMapFromObject` — picks a location/geo field (location-typed, else a geographically-named field) → options.map.locationField. With this, an interface page with `allowedVisualizations: ['gantt']` (or `['map']`, or all seven) resolves and renders. Verified in the showcase: Team Schedule (gantt), Work Map (10 pins), and an All Views page switching across all 7. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub. |
Uh oh!
There was an error while loading. Please reload this page.
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
os-zhuang added a commit
to objectstack-ai/objectstack
that referenced
this pull request
Jun 20, 2026
…config depth, record components) (#2052) Rounds out the showcase so it demonstrates the full page surface, not just a couple of grid interface pages. P1 — every record visualization as its own interface page (task-visualizations.pages.ts): Task Board (kanban) · Task Calendar · Task Gallery · Team Schedule (gantt) · Activity Timeline · Work Map · All Views (switcher across all 7). Each whitelists one visualization and relies on runtime auto-derive for the field bindings; each page's `columns` include the binding fields so the data is fetched. P2 — deeper interface config (active-projects.page.ts): `filterBy` always-on base filter (hide completed) · default `sort` (budget desc) · `addRecord` toolbar form entry point · dropdown user-filters · grid+kanban. P3 — record-layout component set (task-detail.page.ts, full record page): record:path status stepper · record:alert with a `visible` expression (shown only In Review) · record:quick_actions (object actions) · highlights · details. P4 — data so the visualizations look real: cover images on tasks (gallery), reusing the existing lat/lng locations (map). Verified in the browser: all 7 visualization pages render (map shows 10 pins, gallery 10 covers, gantt bars, calendar/timeline/kanban); Active Projects hides the completed project and sorts by budget; the Task record page shows the path stepper, the In-Review alert, and quick actions. Deferred (noted for a follow-up — heavier / uncertain renderers): hierarchy `levels` (needs a self-referencing object + tree renderer) and a `utility`-type panel page. Pairs with objectstack-ai/objectui#1811 (gantt/map auto-derive). Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Interface pages already auto-derive kanban / calendar / gallery / timeline field bindings from the object when whitelisted. This extends the same to the last two record visualizations, so a list/interface page can offer any visualization by whitelisting it alone:
defaultGanttFromObject— start + end date (name-disambiguated, else first two date fields) + optional progress.defaultMapFromObject— a location/geo field →options.map.locationField.Verification
Browser-tested in the showcase: Team Schedule (gantt bars), Work Map (10 location pins), and an All Views page whose switcher now offers all 7 record visualizations (Grid/Kanban/Gallery/Calendar/Timeline/Gantt/Map).
@object-ui/app-shelltsc clean.Enables the framework showcase's per-visualization interface pages (objectstack-ai/framework).
🤖 Generated with Claude Code