Page Property Configuration

Description

Page Property Configuration stores the shared visibility and ordering of fields on a Dotabase's row detail page.

Settings are derived against the live schema, validated so keys still identify real properties, and persisted through the Dotabase service as presentation metadata. The underlying property definitions and values remain unchanged. Because this is the shared page default, every user and surface can begin from one coherent detail-page arrangement.

User Story

As a database owner, I put the essential properties first and hide system fields from the ordinary row page. I submit an ordered set of live property keys and visibility choices. Validation removes ambiguity about which schema the settings describe, and the service stores the shared result. I walk away with a clearer detail page while integrations and alternate views still have access to the complete typed row.

Extension Surface

Configurable: callers set supported visibility and ordering values against live property keys.

packages/dotabases/src/services/page-property-settings.ts is the configuration surface for deriving and validating supported settings. It does not register new renderers or modify the property registry; it arranges existing keys.

Capabilities & Limits

• Capability: Executes the scoped workflow described above through the cited live implementation paths.
• Capability: Preserves typed validation and applicable tenant, schema, lifecycle, or service boundaries.
• Limit: Settings are Dotabase-wide, not a private per-user layout. They do not delete or change property values. The feature can hide or show supported fields and define their shared page order while reconciling against schema changes. It cannot create fields, change types, alter values, or persist a private per-user override. Visual rendering and responsive layout remain responsibilities of consuming applications.

Implementation Map

• packages/dotabases/src/services/page-property-settings.ts
• packages/dotabases/src/services/dotabase-service.ts
• packages/dotabases/src/properties/types.ts

Related Features

Configures Dotabase Workspaces and parallels View Property Personalization.

Operationally, these relationships preserve a clear ownership boundary around Page Property Configuration. Neighboring features can invoke, supply, or consume its results, but `packages/dotabases/src/services/page-property-settings.ts` remains the grounded implementation authority for this capability. That distinction prevents the catalog claim from widening into adjacent rendering, transport, or governance work. Teams can therefore combine the feature with the named dependencies while still diagnosing configuration, validation, and lifecycle behavior at the package boundary that owns it.