You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a target that depends on another target (such as a test target), mayday might show warnings/errors twice. A potential fix for this would be, instead of mayday generating warnings/errors for all source files underneath SRCROOT, for it to be smarter and first make sure that the source file is a part of the target that owns the build phase.
The text was updated successfully, but these errors were encountered:
What I would really love is a way to specify which targets Mayday should be run on, much like a Podspec. That way I could have it run on the main target, but not run on my test targets.
Alternatively, a way to have Mayday run on a given target, but with specific files only, would be wonderful. So, Mayday would only generate warnings for, say, my test target files when run against the test target.
If you have a target that depends on another target (such as a test target),
mayday
might show warnings/errors twice. A potential fix for this would be, instead ofmayday
generating warnings/errors for all source files underneathSRCROOT
, for it to be smarter and first make sure that the source file is a part of the target that owns the build phase.The text was updated successfully, but these errors were encountered: