https://github.com/danielmackay/dotnet-openapi-fully-qualified-schema
https://github.com/danielmackay/dotnet-openapi-fully-qualified-schema
Last synced: 29 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/danielmackay/dotnet-openapi-fully-qualified-schema
- Owner: danielmackay
- Created: 2025-01-18T21:57:52.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-01-19T00:28:27.000Z (over 1 year ago)
- Last Synced: 2025-07-02T22:36:27.619Z (about 1 year ago)
- Language: C#
- Size: 9.77 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# .NET OpenAPI Fully Qualified Namespace
Attempt to reproduce an issue with .NET 9 OpenAPI & Scalar when DTOs with the same class name, but different namespace would cause a conflict.
When using swagger we would solve this by using the namespace to fully qualify the model name in the OpenAPI schema.
## Conclusion
With .NET 9 OpenAPI & Scalar, this is no longer an issue!
Two classes with the same name (i.e. `WeatherForecast`) will automatically have a number suffix added to avoid any conflict.
