[BUG] oas tool 3.0 fail to treat optional field in schema as option.

[cll023]

[BUG] oas tool 3.0 fail to treat optional field in schema as option.

[alesancor1]

I will prioritize this issue for the next 3.0.X version. Many bugs have been reported in the last few months so I'll probably release a patch soon.

[alesancor1]

Yes, some conflicts have emerged in #361, asap they are solved it will be merged. There are some other problems that need to be solved, but they should not take much longer :)

[alesancor1]

I'll look at it. Thanks for providing the code for reproducing the bug, it will make things a lot easier. Could you please edit your comment and add ``` to insert the code in a code block so it is easier to copy? :)

[cll023]

Thanks and fixed . I made a code change and added a test as well. I created a pull request. Please review . Thanks

[pebo]

I'm having the same issue with validation failing for non-required objects. Any chance the #361 could be merged?

[cll023]

Same request here. We can not upgrade to oas tool v3 due to this issue.

[raoulkent]

We've already ported to oas3, and are affected by this issue. Would it be possible to make incremental release as each item is fixed? #361 would be very helpful!

[raoulkent]

That's great to hear. Do you have any time estimate?

I am not so well versed in the source code for OASv3, but please do let me know if there is something easy to pick up. I'd be happy to try and help.

[alesancor1]

@raoulkent I don't want to give any estimate since I am trying to work with many things in parallell, so it depends on the workload I have each moment.

I'd recommend you to read the docs and take some time looking at the code if you can, I tried to make it as easy to read as possible. Then, check the issues and PR and see if you can pick up something there. Also, if you find something isn't clear in docs, feel free to post an issue in the docs repo :)

PS: I merged #361, I'll try to fix the other issues and release a new version soon