Skip to main content

Common Setup Pitfalls

Use this checklist when Widgemo renders incorrectly or behavior is unexpected.

Purpose​

Catch common setup failures early and route directly to the canonical fix location.

Pitfall Checklist​

Missing Required Content Config​

zones.content, mode, and item.fields are required for useful rendering.

Reference: Content Config: Shape

Mode and modeConfig Mismatch​

If mode is chart, configure modeConfig.chart; if mode is board, configure modeConfig.board, and so on.

Reference: Modes Overview

Field Key Mismatch With Data​

If a field key does not exist on entities, rendered output appears empty.

Reference: Field Config

Overriding Host CSS in Table Scenarios​

Global host table styles can override Widgemo table appearance and interaction affordances.

Reference: Host CSS and Table Layout

Action Overflow Expectations​

If actions collapse into overflow unexpectedly, verify actionOverflow.maxInline values and viewport behavior.

Reference: Action Config: Action Overflow

Responsive Breakpoints Not Applying​

Verify content.responsive.breakpoints keys and that each breakpoint override aligns with the target mode.

Reference: Responsive Switching

Gesture Handlers Not Firing​

If a local gesture onTrigger is absent, events fall back to interactions.onEvent.

Reference: Content Config: Gestures

Inspecting the Applied Configuration​

When a pitfall is hard to diagnose from code alone, use the Widgemo Inspector. It shows the resolved config that Widgemo is actually running — including inferred defaults, mode settings, and active field declarations — which makes it straightforward to spot mismatches between what you wrote and what the Widgemo received.

The Inspector is available in development by default. See DevMode for setup details and how to enable it in non-development environments.

Quick Recovery Path​

  1. Start from a minimal table config.
  2. Add one feature at a time.
  3. Validate each change before adding the next.

Next Steps​

  1. Re-validate your base setup with Installation
  2. Confirm a working baseline in Quick Start
  3. Reapply changes in Your First Widgemo order