OpenAPI: Beginner to Guru (Udemy.com)

I learned a lot and believe this was worth the time to learn about the basics of API's. I am not sure I, as a basic learner, could tell you how to make the course better. However, I think a tie from a real-world example would have been great at points along the way. Show me a real-world example of how the API really worked. A web page that showed me the before and after. Ability to get, put, etc. Access granted versus blocked. I did like seeing how the code was going to change things, but as a beginner, what and why does it matter?

The course treats the topics very clearly and smoothly. Easy to follow. The topic is also very specific and it's difficult to find courses about it on the web. Thanks for having provided a course about it. Very helpful. The course could improve in the following aspects - Provide more visuals. Bunch of static slides can be boring after a while. - Show in simple terms the big picture of the end product of a Web Application identifying where exactly the OpenAPI documentation is located within the workflow.

It was very good. But i have seen that when i use maven extensions, the code gets generated in target folder, which seems to be correct since, yaml file keeps changing. but the code generated by open api code gen is actually in the main folder. can you tell me why? how to solve this problem? what the standard operating procedure for spring boot projects?

This course is awesome! I would like to see this in action on some real life example in IDEA, where you put dependencies for OpenAPI in Gradle(maven) and step by step do the whole process and code generation at the end . I've learned a lot from this course, but as I said, as a Java Junior developer, it would be a great thing to see the whole thing like that what my colleagues do everyday. It could speed up my productivity. :)

Watching the course is definitely nicer than having to read through the documentation yourself, and I know it would be difficult to offer something truly engaging on this topic. The course is detailed, gives examples of usage, covers YAML and some background. As regards possible improvements, I haven't found any info on the use of OpenApi annotations in Java (such as @ApiModelProperty), which might be valuable for Java developers. I think the author could easily cover this topic. Callbacks might be explained better, instead of providing a link to another website. The heavy reliance on the documentation would be easier to accept if there were more graphical materials provided by the course author to make it more varied, focus on what is actually covered.

Thank you so much for this course was very helpful on learning the Open API 3.0 specification that other resources online fail to cover as I tried and ended up only finding outdated material on swagger or open api 2.0. There is a lot of ground to cover in Open API 3.0 but I believe you give a strong core knowledge that should give anyone enough to get started and figure out more advance topics that apply to their application.

This is a great course. I learned the OAS 3 and swagger from this course. Before purchasing this course, i tried to learn for other things from internet but cannot find anything good for beginneer to start. So it was very confusing for me to start. But this course really helped to integrate rest api. I am going to use this knowledge for my express node projects. Thanks Guru.

First of all, thank you John for adding course on OpenAPI specification. I was searching for this so long on Udemy for learning about OpenAPI in details. You covered almost all of the basic requirements as well as some of the advanced topics. So, it was great and every topics are cleared to me. Just one thing, it will be helpful if you can add a small course for Java/Spring Developers on customised OpenAPI docs using Java code (i.e, Spring Doc API specification). :-)

It begins bit confusing if you don't know anything about HTTP but gets better and better. It is so helpful going through all of the OpenAPI specification under his guidance. He points out what is important, alternative resources, etc.. At the end you get a very fulfilling feeling.

Course was what I was expecting. By the middle of the course, I was comfortable completing the exercises on my own without having to go back and review previous material. I observed the API specifications provided in the Resources did not exactly match what was created in the sessions - items were added that were not covered in the sessions and there were errors in some example specifications. For instance: Styles were used and some responses were not formatted correctly (e.g. 200: instead of '200':). I also experienced problems with the Swagger editor. I received frequent notifications that the specification I was using did not contain a correct version number (even though it did), causing me to have to delete the file and either create a new one or upload a yaml file from the resources.