Replies: 4 comments 5 replies
-
OMG yea I have found that to be really annoying too. I've done every single thing I could in Tuist configurations but to no avail. At this point I'm in the acceptance phase but I'd definitely be happy to see those other schemes disappear :D |
Beta Was this translation helpful? Give feedback.
-
@kamcma Can you specify which schemes in particular? We currently have some checked in that were needed for the Swift Package Index to detect whether or not TCA built for watchOS, but perhaps we can git ignore some of the others? Just want to be sure of what you're seeing, exactly, to understand the problem. |
Beta Was this translation helpful? Give feedback.
-
This is what I'm seeing. |
Beta Was this translation helpful? Give feedback.
-
@stephencelis thank you SO much for merging this! What a nice surprise; I wasn't expecting this to be addressed for a while, with all the other conversations going on in parallel. My schemes list is so clean now :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It's not a huge issue, but I have occasionally been puzzled by schemes from the TCA package showing up in my schemes list in dependent projects.
I can't pretend to be an Xcode expert by any means, but I did find this PR in the
swift-collections
package to be clarifying: apple/swift-collections#155.Do you think this is the same thing happening with TCA? Is TCA vending these schemes deliberately? Anyway, just wanted to share in case this was a bit of deferred maintenance. If there's a reason for it, however, I'd understand, and carry on.
Beta Was this translation helpful? Give feedback.
All reactions