-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Rolodex.Resolve() doesn't override the description from #ref definition #262
Comments
There is a known bug in the resolver that appears haphazardly when resolving async extracted refs (which is the default). The solution (until the root cause is fixed). Is to extract references synchronously by setting the https://github.com/pb33f/libopenapi/blob/main/index/index_model.go#L149 |
Hi @daveshanley, thanks for responding. I've tried the configuration, but it didn't work. |
Oh, sorry, I mis-read your problem. The result you have is the expected outcome of how the resolver works. It's not performing any kind of property merging or overriding, it's simply resolving the references, literally by re-pointing the underlying node tree. It's resolving like a compiler resolves pointers, it is not going to deliver what you're looking for. This would be a new feature. |
Got it, thanks for the feedback. Ok, I thought it was a bug because of the way it was defined in the 3.1 Reference Object documentation. Do you want me to open another issue as a feature request? |
yes please! |
This is somewhat related to this issue #90 |
Hello, it seems like the Rolodex.Resolve() method doesn't override the description from #ref definition and resolving all refs.
I have the following spec example:
After outputting the result I got this:
The expected output is:
This is the code I am using:
The text was updated successfully, but these errors were encountered: