[Copilot]

Compiler-generated XML references snippet files that aren’t included in compiler output, leaving unresolved examples in generated ECMAXML. This proposal outlines a standalone importer; no repository files or tool code were changed.

• Discovery and resolution

  • Detect XML and Markdown snippet references.
  • Use SourceLink metadata to resolve paths against the original source file at the matching revision; report ambiguous mappings.

• Import and reference updates

  • Copy complete snippet files into a deterministic layout.
  • Rewrite documentation paths while preserving region selectors.
  • Deduplicate imports and guard against path escapes and conflicting destinations.

• Operation and scope

  • Support local checkouts or commit-pinned downloads, dry runs, strict mode, and provenance reports.
  • Defer project-file copying and compilation support to a subsequent phase.

• Fixes [Code snippet importer] Add tooling to import code snippet files #805

[Copilot]

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

[gewarren]

@copilot Please go ahead and generate a prototype of the tool.

[Copilot]

@copilot Please go ahead and generate a prototype of the tool.

Implemented in 3b9fb85. The prototype imports XML and Markdown snippet references from a local checkout using an explicit DocId source map, preserves selectors, and supports dry runs and safe path checks. Usage and deferred SourceLink/project-file support are documented. Validation: 113 tests passed, two existing skips; manual CLI checks passed; no secret-scanning or CodeQL findings.