Marek Fořt

For the `****-project` scheme, I think we can add an API to configure that directly. However, having `Workspace(projects: .default)` might still be useful as it's IMHO rare case where one...

Hey, @leogdion! We tried to stay close to what [SwiftGen](https://github.com/SwiftGen/SwiftGen) does and they don't have support for SwiftUI images just yet. I am not against deviating from their template but...

Hey @arunrdd 👋 Yes, I think it makes sense to support both. However, as a user you might want to make SwiftUI or UIKit the default, so it's more convenient...

> Not sure I follow this part. Typically you'll need to explicitly declare all the direct dependencies of your target, the generation logic will ensure to include transitive dependencies where...

> as far as I can see, currently we generate bundle accessors only for Swift Correct, we don't have such logic for Objc - this would need to be added...

Hey @nugmanoff! I think this is an interesting idea, but I'm hesitant about adding this a new option as I'm not sure if it brings enough value to justify for...

> Is it possible to do something similar for targets easily? Yeah, I think so. The final order should be based on the order we generate targets. If we order...

Hey @rafagan! This looks like a valid issue - would you like to take a stab at fixing this? I can provide you with some pointers if necessary.

Awesome! There's a general [getting started guide](https://docs.tuist.io/contributors/get-started) for contributors. After you get the initial setup ready, I'd suggest reproducing this in a unit test/example project and inspecting the logic in...

I am not aware of this - afaict, the plist will eventually be generated via [this](https://github.com/tuist/tuist/blob/main/Sources/TuistGenerator/Generator/InfoPlistContentProvider.swift) file and there's no mention of `CFBundleSupportedPlatforms` 🤔 Maybe we need to add that...