fix: improve performance of XcodeGraphMapper #111
Merged
Conversation
This file contains hidden or 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
fortmarek
force-pushed
the
fix/performance-graph-mapper
branch
from
bbbcec3 to
4d69b8a
Compare
ajkolean
requested changes
Feb 7, 2025
Sources/XcodeGraphMapper/Mappers/Project/PBXProjectMapper.swift
Outdated
Show resolved
Hide resolved
Co-authored-by: Andy Kolean <andykolean@gmail.com>
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.
When I ran
XcodeGraphMapperontuist/tuist, it was very slow. Mapping projects concurrently improves things a ton and thanks to the functional mapper approach, doing this is a couple of line. We can consider running more granular mappers if the performance would be still an issue for large projects.