Ian Leitch
Ian Leitch
Just an FYI that this issue was a blocker for me adopting `rules_swift_package_manager`.
My aim was to add Bazel module support to https://github.com/peripheryapp/periphery, however a key place I tried to use it is a private iOS app already using `rules_swift_package_manager`. Essentially the same...
Why are you using the `--index-store-path` option? Does the generated baseline file contain anything?
This issue should now be resolved in 3.0.0. Let me know if you continue to experience this issue and I will reinvestigate.
@AF-cgi This file is not scanned because Periphery excludes paths matching the pattern `**/*?.build/**/*`. Unfortunately, I don't think relaxing this pattern to allow `GeneratedAssetSymbols.swift` to be scanned is necessarily the...
@Lommelun If you can provide an example of a package plugin that generates sources, I can take a look.
Thanks for reporting this @mayoralito. I'm unable to reproduce the warning with the example you provided. Could you please create a simple Xcode project that demonstrates the issue?
You're correct that it should identify NSObject subclasses by default. Are you seeing this for all subclass or just some? If you can provide an example project that reproduces the...
Closing this as there's nothing for me to investigate. If you're able to isolate the problem in a sample project, that'd be great.
Hi @bosnian, does your project contain private packages?