Dashboard: Add collapsible sections support to Open API (v2)

Open
#1,901 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api

Research direction

Start with the external API Zod schemas in packages/api/src/utils/zod.ts, then locate ExternalDashboard, ExternalDashboardTileWithId, convertToExternalDashboard, and the dashboard create/update flows. Verify how sections and tile sectionId are represented by the internal API and frontend. Done means GET, POST, and PATCH expose and preserve these fields, with applicable OpenAPI or Swagger documentation updated.

Written by the indexing model from the issue text.

Description

Summary

The internal API and frontend now support collapsible dashboard sections (#1896, #1897). The external/Open API (v2) should be updated to expose this capability so users can programmatically create and manage dashboards with sections.

Scope

Read path (GET)
  • Add sections field to ExternalDashboard type
  • Add sectionId field to ExternalDashboardTileWithId type
  • Update convertToExternalDashboard to include sections and tile sectionId
Write path (POST/PATCH)
  • Add sections to the external dashboard input validation schemas
  • Add sectionId to the external tile input schemas
  • Pass through sections in create/update flows
Schema / docs
  • Update the external API Zod schemas in packages/api/src/utils/zod.ts
  • Update any OpenAPI/Swagger documentation if applicable

Dependencies

  • #1896 (core mechanics) — merged or in progress
  • #1897 (authoring UX) — ideally landed first so the feature is fully usable end-to-end before exposing via API
Dominant language
TypeScript
Stars
9.9k
Forks
471
Avg merge
2d 4h
Merged PRs (30d)
117

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyperdxio/hyperdx

All issues in hyperdxio/hyperdx

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.