-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Schema reference path has not been resolved' in path referenced yaml file #3175
Comments
Any update to this? |
I stuck to the 13.6.x version and haven't tried it with a more recent version lately. |
I have the feeling this might have been fixed with this PR: Please try again with v13.10.4+ |
I get the exact same issue when trying to generate a C# client based on a public Swagger 2.0 yaml specification. I'm using version 13.11.3 of the Nuget packages NSwag.CodeGeneration.CSharp and NSwag.Core.Yaml
Exception has occurred: CLR/System.InvalidOperationException Any help would be appreciated |
Same issue with 13.20.0.
|
I`ve found that external references works only for section #/definitions First reference from A to B works well, but all other references in B must point to #/definitions section (https://json-schema.org/draft-07/schema#) |
When generating C# client code with the NSwag command line toolchain 13.9.2 Netcore31 from
root.yaml:
path.yaml:
object.yaml
I get the following error:
I saw that path reference support was added recently (#1953). When recreating the same case in ExternalReferenceTests.cs / path-reference.json no error is given.
When generating from the same files with the 13.6.0 toolchain no error is given and the code is correctly generated.
The text was updated successfully, but these errors were encountered: