-
Notifications
You must be signed in to change notification settings - Fork 938
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
Specification for Abstract methods #1365
Comments
Strange. There isn't anything that cares about abstract.. Could you post a simple self-contained example to reproduce this? I am not sure I understand what 'OA annotations on top' means. An operation like get/put I would assume? I presume there are also controller classes processed that contain the actual implementations? Are those annotated too? |
Ok let me give more info for complete picture. The folder structure is following:
Code piece from
Code piece from
But the scanner is pointed to the
This will echo out only the first method specification and not for others:
|
I got more insights that can help to figure out the issue. If there is a class with several abstract and non abstract methods like the example below:
The specification will be generated for |
That sounds like an awesome clue! It is possible that the |
Thanks @DerManoMann, I'll check and will post here |
The fix on #1369 works perfectly |
I have several abstract methods in the class:
When I generate the specification, then only the
signin()
method specification is getting generated.Looks like it doesn't generate specification for abstract methods (other then the first one), because if I change the last one to be non abstract like:
Now specification is getting generated for 2 methods
signin()
andsignout()
.The text was updated successfully, but these errors were encountered: