dead-code-hunter Architecture Docs
Home / Subdomain/ InputMapping — dead-code-hunter Architecture

InputMapping — dead-code-hunter Architecture

Subdomain GitHubAction InputMapping 2 files

Parses YAML-defined inputs into usable TypeScript configuration objects.

Entity Profile

Dependency Diagram

graph TD
  subdomain_GitHubAction_InputMapping["InputMapping"]
  1916269f_4df6_c8ce_0c1a_a8a66a4fb245["index.ts"]
  subdomain_GitHubAction_InputMapping --> 1916269f_4df6_c8ce_0c1a_a8a66a4fb245
  ad094038_3d51_d844_e2ec_7f4735d9d0f1["dead-code.test.ts"]
  subdomain_GitHubAction_InputMapping --> ad094038_3d51_d844_e2ec_7f4735d9d0f1
  style subdomain_GitHubAction_InputMapping fill:#6366f1,stroke:#818cf8,color:#fff

Relationship Graph

Domain

Functions

Source Files

Source

Frequently Asked Questions

What is the InputMapping subdomain?
InputMapping is a subdomain in the dead-code-hunter codebase, part of the GitHubAction domain. Parses YAML-defined inputs into usable TypeScript configuration objects. It contains 2 source files.
Which domain does InputMapping belong to?
InputMapping belongs to the GitHubAction domain.
What functions are in InputMapping?
The InputMapping subdomain contains 7 function(s): createZipArchive, filterByChangedFiles, makeCandidate, makeMetadata, run, safeSerialize, sleep.

Analyze Your Own Codebase

Get architecture documentation, dependency graphs, and domain analysis for your codebase in minutes.

Try Supermodel Free