René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Warn when import-mapping keys are JSON pointers instead of document paths","articleBody":"In #2078 a user wrote:\n\n```yaml\nimport-mapping:\n  \"#/components/schemas\": mymodule/internal/dto\n```\n\nexpecting internal component refs to be remapped to another Go package. `import-mapping` keys are external document paths (files or URLs), not JSON pointers, so an entry like this silently never matches anything — the user just sees unresolved types with no hint about why.\n\nTwo small improvements:\n\n- Configuration validation should reject (or warn on) `import-mapping` keys starting with `#`, with a message along the lines of \"import-mapping keys are document paths; internal refs cannot be remapped — see the import-mapping examples\".\n- The README section on `import-mapping` should state explicitly that keys are document paths, that internal `$ref`s always resolve to the current package, and point at `examples/import-mapping/` for the two supported layouts (separate packages via spec split, same package via the `\"-\"` mapping).\n","author":{"url":"https://github.com/mromaszewicz","@type":"Person","name":"mromaszewicz"},"datePublished":"2026-07-13T00:27:19Z","url":"https://github.com/oapi-codegen/oapi-codegen/issues/2459"}