René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Self-contained generated code with no external runtime dependencies","articleBody":"I’d like to propose support for generating code that is fully self-contained, without depending on external runtime/helper packages.\n\nTo reduce dependency footprint and supply-chain risk, I would strongly prefer generated output that relies on the Go standard library wherever possible, rather than importing additional packages for helpers, types, validation, marshaling, parameter binding, and other runtime behavior.\n\nThe main motivation is to make generated code easier to adopt in stricter environments where we want:\n\n- fewer external dependencies\n- simpler auditing and vendoring\n- less version coupling between generated code and helper libraries\n- more explicit, verbose generated logic instead of hidden/runtime behavior\n- code that is easier to copy, inspect, and maintain internally\n\nIn short, we would prefer the generated code to be self-contained, even if that means the output is more verbose.\n\nA few thoughts on scope:\n\n- a config option for “self-contained” or “no runtime deps” generation would be ideal\n- generated code could inline helper types/functions instead of importing them from external packages\n\nI realize this may involve tradeoffs in generated code size and maintenance burden, so I wanted to ask first whether this direction would be welcome.\n\nIf the project is open to receiving this change, I’d be happy to contribute an implementation.","author":{"url":"https://github.com/tigrato","@type":"Person","name":"tigrato"},"datePublished":"2026-04-29T12:05:24Z","url":"https://github.com/oapi-codegen/oapi-codegen/issues/2342"}