Skip to content

feature_request.md

Latest commit

 

History

History
43 lines (32 loc) · 1.82 KB

feature_request.md

File metadata and controls

43 lines (32 loc) · 1.82 KB
Raw
name Feature request
about Propose a new feature, public API addition, or template
title [FEATURE]
labels enhancement

Use case

Proposed API

// Sketch the public-API shape you'd like to use. Stick to the canonical surface:
//   authoring        GraphCompose.document(...) -> DocumentSession, document.pageFlow(...)
//   new visual node  DocumentNode (com.demcha.compose.document.node)
//                    + NodeDefinition (com.demcha.compose.document.layout)
//   theming          BrandTheme (com.demcha.compose.document.templates.core.theme)
//   new output kind  FixedLayoutBackendProvider (…document.backend.fixed)
//                    or SemanticBackend (…document.backend.semantic)
document.pageFlow().add???(...);

Alternatives considered

Would this be a breaking change?

Classify the surface it touches against docs/api-stability.md (§1 defines the tiers, §4 maps each package onto one).

  • No — additive only (new node, new builder method, new template preset).
  • Possibly — affects public-record shape, deprecates an existing API, or changes default rendering behaviour.

Optional: ADR-worthy?

If this is a structural change (sealed hierarchy, new sub-package, new SPI), please describe the architectural impact briefly. The maintainer may ask for a draft ADR under docs/adr/ before implementation.