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
Support for parenthesized type declarations #102
Comments
I'll take a look at this. Thanks for reporting it. |
Thanks. If you could provide some direction I wouldn't mind taking a crack at a PR. |
Actually I would have to see how the AST represents this specific problem. Let me make a couple of tests to see if I can suggest a COA. Thanks for this and sorry for the delays in my responses. I think I have to hook some notifications in this repo. I only see these updates if I come to github. |
I just took a look at this. In the fileparser/class_parser.go near to line 320 the code assumes the dec.Specs array will only contain 1 element. I have never seen the declarations as you posted in this issue and of course never ran into this case. If you wrap the code from 321 to 370 around a for loop range on each Spec you will solve this issue. :) |
Wrapped code to parse types inside a loop instead of just doing the first.
I had several parenthesized interface type declarations and noticed they weren't showing up in the puml output.
Examples)
Works:
Not working:
The text was updated successfully, but these errors were encountered: