[iOS] Not to use SwiftGenPlugin package to avoid high cpu usage #88
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ry-itto
force-pushed
the
workaround-high-cpu-usage-on-spm-plugin
branch
from
471c982
to
430280a
Compare
pchmelar
reviewed
Sep 14, 2022
Comment on lines
+7
to
+8
| let configurations: [Path] = [context.package.directory, target.directory] | ||
| .map { $0.appending("swiftgen.yml") } |
There was a problem hiding this comment.
Hey 👋 Thanks for this temporary workaround, it worked great in Xcode 13. However, in Xcode 14 we experience issues, because it is looking for the swiftgen.yml config file in both places and if one of them doesn't exist, the whole command fails.
The solution is to add .filter { FileManager.default.fileExists(atPath: $0.string) }.
Thanks to @Carrione for this idea! 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
related issues:
According to these issues, artifact-bundle causes this problem, but it isn't caused by artifact-bundle in my environment. So I will use own plugin instead of plugin package experimentally.