-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
IBActions reported as unused #234
Comments
Servus 👋 That certainly shouldn't be happening. We've already test coverage for IBAction: https://github.com/peripheryapp/periphery/blob/master/Tests/XcodeTests/iOSProject/iOSProject/XibViewController.swift#L4-L7 So there must be something a little different about your usage. Could you take a look again and see if there's any special about the way you're using IBAction perhaps? If not, please provide an example. |
I see the same issue if my |
In my project, I don't have false positives for my |
I'm also unable to reproduce this by making them private.
Are you using the new |
I added |
@Servus7 That option is only intended for use with mixed Swift/Objc projects. It shouldn't be used just to fix IBAction false positives. If a class is referenced by a nib, then it's IBActions should also be identified as used. Do you have any instances of IBAction being reported as unused in a class that also has IBOutlet/Inspectable that aren't being reported as unused? If so, please provide as much code as possible from this class so that I may diagnose. |
We were using Resources Bundles and doesn't added them to periphery scan 🤦🏻♂️ |
All IBActions In our project are incorrectly marked as not used. IBInspectable and IBOutlet however are marked only if unused.
What could be the difference resulting in all IBActions being false positives?
The text was updated successfully, but these errors were encountered: