Scope & discovery

These knobs decide the inputs and the surface of the scan: which packages codescan reads, which types become definitions, and how that set is trimmed or merged before anything is rendered.

• Scoping the scan

  Limit what gets scanned — package patterns, working directory, include/exclude filters, tag filters, and dependency handling.
• When the scanner emits a type

  codescan never invents definitions — a type appears only when it is reachable or registered. Understand reachability and swagger:model so nothing goes missing or appears unexpectedly.
• Pruning unused models

  Scan a shared library with swagger:model discovery, then keep only the definitions actually reachable from your API — the middle ground between “only what routes use” and “every model, used or not”.
• Overlaying a spec

  Merge scanned discoveries on top of an existing Swagger document with InputSpec.
• Build tags

  Scan source guarded by Go build constraints by passing build tags to the scanner.