GFramework/tools/gframework-config-tool

GFramework Config Tool

VS Code extension for browsing, validating, and lightweight editing in the GFramework AI-First config workflow.

Purpose

This extension is the editor-side companion for the GFramework.Game config pipeline:

• config/**/*.yaml
• schemas/**/*.schema.json
• source-generated config types and tables

It is intended to speed up browsing, validation, lightweight form editing, and domain-level maintenance inside VS Code. It is not a replacement for the runtime or generator packages, and it does not attempt to be a full JSON Schema editor.

Recommended Workspace Layout

By default, the extension expects:

GameProject/
├─ config/
│  ├─ monster/
│  │  ├─ slime.yaml
│  │  └─ goblin.yaml
│  └─ item/
│     └─ potion.yaml
└─ schemas/
   ├─ monster.schema.json
   └─ item.schema.json

What It Adds

Explorer View

• Browse config files from the first workspace folder's config/ directory
• Group files by config domain
• Open matching schema files from schemas/

File-Level Actions

• Open raw YAML
• Open the matching schema
• Open a lightweight form preview
• Revalidate saved config files automatically when they change

Domain-Level Actions

• Batch edit one config domain across multiple files for top-level scalar and scalar-array fields
• Validate all discovered config files from the explorer view

Form / Validation Support

• Localize extension UI text in English and Simplified Chinese, including the form preview, prompts, and notifications
• Render existing YAML comments in the form preview and edit per-field YAML comments directly from the form
• Jump from reference fields to the referenced schema, config domain, or direct config file when a reference value is present
• Initialize empty config files from schema-derived example YAML
• Edit nested object fields recursively inside the form preview
• Edit arrays of objects in the form preview, including nested object fields inside each item
• Surface schema metadata such as title, description, default, enum, and x-gframework-ref-table in the lightweight editors

Validation Coverage

The extension currently validates the repository's current schema subset:

• required properties in nested objects
• unknown properties in nested objects
• scalar compatibility for integer, number, boolean, and string
• scalar arrays with scalar item type checks
• arrays of objects whose items use the same supported subset recursively
• scalar enum constraints and scalar-array item enum constraints
• scalar const constraints
• numeric range constraints such as minimum, exclusiveMinimum, maximum, exclusiveMaximum, and multipleOf
• string constraints such as minLength, maxLength, and pattern
• array constraints such as minItems, maxItems, contains, minContains, maxContains, and uniqueItems
• object constraints such as minProperties, maxProperties, dependentRequired, dependentSchemas, allOf, and object-focused if / then / else
• closed-object validation through additionalProperties: false
• explicit rejection for unsupported combinators such as oneOf and anyOf, instead of silently ignoring them

Contract Boundary

This extension is an editor-side helper. It does not define the runtime contract for GFramework.Game.

• The runtime and source generator remain the source of truth for which schema shapes are formally supported
• The VS Code experience mirrors that shared subset so unsupported shapes fail early during browsing or validation
• If a shape is too complex for the lightweight editors, fall back to raw YAML and the schema file first; do not assume the runtime accepts a broader contract just because the editor has no custom form for it

Workspace Settings

{
  "gframeworkConfig.configPath": "config",
  "gframeworkConfig.schemasPath": "schemas"
}

Quick Start

1. Install the extension in VS Code and open the workspace that contains your config/ and schemas/ directories.
2. Keep the default workspace layout, or set gframeworkConfig.configPath and gframeworkConfig.schemasPath to your project-specific paths relative to the first workspace folder.
3. Open the GFramework Config explorer view and select a config file or domain.
4. Run validation first to confirm the current YAML files still match the supported schema subset.
5. Open the lightweight form preview or domain batch editing actions, then fall back to raw YAML for deeper nested edits when needed.

Use raw YAML directly when you need:

• deeper or more heterogeneous array shapes
• object rules centered on allOf, dependentSchemas, or object-focused if / then / else
• contains / minContains / maxContains verification on structures that are easier to reason about in source form
• schema designs outside the current shared subset, including oneOf, anyOf, or non-false additionalProperties

Documentation

• Chinese adoption guide: Game 配置工具
• Related config runtime guide: Game 配置系统

Current Constraints

• Multi-root workspaces use the first workspace folder
• Validation only covers the repository's current schema subset
• Form preview supports nested objects and object-array editing, but deeper nested object arrays inside array items still fall back to raw YAML
• Batch editing remains limited to top-level scalar fields and top-level scalar arrays
• Closed-object support is limited to additionalProperties: false, and unsupported combinators such as oneOf / anyOf are rejected on purpose

Local Testing

cd tools/gframework-config-tool
bun install
bun run test

Packaging And Publishing

cd tools/gframework-config-tool
bun install
bun run package:vsix
VSCE_PAT=your_marketplace_pat bun run publish:marketplace