feat: Add automatic wildcard content type support#1579
Merged
ernado merged 1 commit intoogen-go:mainfrom Nov 24, 2025
Merged
Conversation
Add optional wildcard content type support to enable code generation for APIs using */* or application/* in OpenAPI specs. - Add WildcardContentTypeDefault configuration option (opt-in) - Implement wildcard detection and mapping in gen_contents.go - Preserve binary stream handling for format: binary - Add comprehensive test coverage for wildcard scenarios - Enable previously failing k8s.json and redoc specs The feature is backward compatible (disabled by default) and allows users to specify a default encoding (e.g., application/json) for wildcard content types via YAML configuration. Fixes #2
e2a7c2c to
021939f
Compare
ernado
approved these changes
Nov 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds configurable wildcard content type support (
*/*,application/*) to enable code generation for APIs that use wildcards in OpenAPI specs.Fixes #2
Changes
wildcard_content_type_defaultconfiguration option (opt-in)application/json)format: binaryschemasConfiguration
Without config: Wildcards fail as unsupported (backward compatible)
With config: Wildcards map to configured type and generate successfully
Testing
*/*,application/*, and mixed scenariosImpact
Enables code generation for ~15% of real-world carrier/logistics APIs that previously required skipping operations due to wildcard content types.