You are right, for Spring Boot, the relatively new springdoc supports javadoc[1] as descriptions, which is better than the annotation. [1] https://springdoc.org/#javadoc-support
For the happy path, the Java code works great, but a good open API spec also includes the following: - examples, they are a pain to write in Java annotations. - multiple responses, ok, invalid id, not found, etc. - good…
I think that they put the user information in the image using something like this[1]. [1]. https://github.com/subc/steganography
Location: Asunción, Paraguay Remote: Yes Willing to relocate: Maybe Technologies: Java (EE and spring), Javascript, Docker Résumé/CV: https://www.volpe.com.py/cv, https://github.com/avolpe, https://www.volpe.com.py…
You are right, for Spring Boot, the relatively new springdoc supports javadoc[1] as descriptions, which is better than the annotation. [1] https://springdoc.org/#javadoc-support
For the happy path, the Java code works great, but a good open API spec also includes the following: - examples, they are a pain to write in Java annotations. - multiple responses, ok, invalid id, not found, etc. - good…
I think that they put the user information in the image using something like this[1]. [1]. https://github.com/subc/steganography
Location: Asunción, Paraguay Remote: Yes Willing to relocate: Maybe Technologies: Java (EE and spring), Javascript, Docker Résumé/CV: https://www.volpe.com.py/cv, https://github.com/avolpe, https://www.volpe.com.py…