-
Notifications
You must be signed in to change notification settings - Fork 105
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
Fixed interface plugin linemarker #328
Conversation
Please check the first commit in this PR (ref: a17b6a3) to find my proposed solution. The other commit adds too many static test fixes. Also, I was thinking if the below code would be a better approach than the one in the above commit. This code would get both classes and interfaces, for the given FQN, instead of just getting interfaces only if classes returned empty. Is there a case where the below code would be required? Just bouncing off ideas, thanks.
|
This PR edits a single line of a file where there are 10s of pre-existing static test failures. I shall fix those failures once my suggested approach is confirmed by a reviewer. Thanks! |
@drpayyne I'm fine with the solution. Please proceed. |
Hi @VitaliyBoyko, could you please advise on how I can fix the remaining static test failures? I'm not sure what's the good approach.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description
This PR fixes the missing linemarker for plugins to interface methods
Fixed Issues
Questions or comments
I have a proposed solution, but if anyone has a better solution, please do let me know. I shall improve it.
Contribution checklist