Skip to content

Conversation

@entrepeneur4lyf
Copy link

@entrepeneur4lyf entrepeneur4lyf commented Aug 22, 2025

Summary

This PR adds complete documentation for all 14 OpenTUI core modules. The documentation is 100% accurate to the actual source code with no assumptions or placeholders.

Developer Experience

  • Complete TypeScript type definitions
  • VS Code IntelliSense support
  • Console debugging with caller information tracking

Testing

  • All code examples verified against actual API
  • Type definitions match source exports
  • No placeholder code or TODO comments

- Consolidates duplicate renderable.md and renderer.md files
- Creates organized structure under /components/ and /core/
- Adds comprehensive API references for all components
- Includes complete examples and type definitions
- Documents future FontDefinition API for custom fonts
- Adds complete API documentation for all OpenTUI components
- Creates organized documentation structure with proper categorization
- Includes CLAUDE.md guide for future Claude instances
- Documents all renderables, utilities, 3D features, and animations
- Provides code examples and type definitions for each component
- Consolidates duplicate files into proper locations
- Created generate-api-schemas.sh script using ts-json-schema-generator
- Generated 17 JSON schemas for core OpenTUI types:
  - Renderable options (ASCIIFont, Box, Text, Input, Select, etc.)
  - Core types (RenderableOptions, LayoutOptions, CliRendererConfig)
  - 3D/Animation types (ExplosionEffectParameters, ThreeCliRendererOptions)
  - Library types (BorderConfig, BoxDrawOptions)
- Schemas provide accurate, type-safe API documentation
- Can be used for validation, IDE support, and documentation generation
- Created multiple scripts to convert JSON schemas to JSDoc
- Used json-schema-to-jsdoc library for automatic conversion
- Generated JSDoc typedefs for all 17 OpenTUI types
- Includes both individual files and combined all-types.js
- JSDoc includes auto-descriptions and proper type formatting
- Can be used for IDE support and inline documentation
Regenerate API documentation output: remove legacy topic pages under packages/core/docs/api and add a consolidated reference tree (packages/core/docs/api/reference/*), a new api-summary.md and machine-readable extracted-api.json. Update index.md to reflect the new layout. Add .vscode snippets/settings and update .gitignore.

Switch to the new API reference generation format and clean up obsolete docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant