SECTION nodes do not include exportSettings in REST API response #87

Summary

When calling GET /v1/files/:key, nodes of type SECTION are returned without the exportSettings property, even when those sections have export settings configured in Figma.

Other node types that support export settings (e.g. FRAME, COMPONENT, INSTANCE) correctly include exportSettings in the API response. SECTION nodes in the same file—with the same export presets configured in the UI—omit this property entirely.

Expected behavior

SECTION nodes that have export settings in Figma (configured via the Export panel) should include exportSettings in the GET /v1/files/:key response, consistent with other node types that implement the HasExportSettingsTrait.

Actual behavior

SECTION nodes are returned without exportSettings. The property is absent; it is not an empty array.

Reproduction

1. Create a Figma file with a page that has SECTION nodes
2. Add export settings to one or more SECTION nodes (e.g. PNG @2x)
3. Call GET /v1/files/:key for the file
4. Inspect the SECTION nodes in document.children[*].children

Observed: SECTION nodes have no exportSettings key. FRAME nodes with export settings in the same file correctly include exportSettings.

Additional context

• This affects any client that relies on the file JSON to discover which nodes have export presets (e.g. bulk export tools, design-to-code pipelines)

Spec / docs

If the spec intentionally excludes SECTION from nodes that may have exportSettings, it would help to document that. If SECTION should support export settings (as in the Figma app), the API behavior may be inconsistent with the spec.