Marek Fořt

Hey @thebarndog 👋 That's a reasonable addition. Would you want to contribute to this? > that are able to generate a standalone watch app or watch targets in general? I'm...

Hi @innoreq! > However, we could not export the keychain's private key as .p12, but only as .pem. Do you know why that is not possible? > We assume that...

Hey @cccCody 👋 We save `1` as `.boolean(true)` [here](https://github.com/tuist/tuist/blob/main/Sources/ProjectDescription/Environment.swift#L21) and we never treat it as a string from that point on. My suggestion would be to save the original value...

> I wanted to avoid basically fetching every time on CI so a cache could be used as I noticed switching to Dependencies.swift with fetch massively increased CI time over...

> However, does seem like it might be useful to everyone built into the generate command like you described. Yeah, in this case I think it's worth adding to `generate`...

Hi @bvirlet - afaict you can change the derived data location globally in Xcode, it's not something saved in `.pbxproj`. If you change your path globally, the snippet @luispadron has...

You can also change the custom derived data path globally to a relative path as per the image: . Does that fix your problem?

Right, I see what you mean. I think we could create a new [generation option](https://docs.tuist.io/manifests/config#generationoption) such as `derivedDataPath: Path` that would count with the custom derived data path during the...

Awesome! Yes, you can basically follow that option and add `derivedDataPath` there as well, I don't think it differs much in how we should handle it.

Hi @zdnk, I agree it is not ideal to have to regenerate a project, especially early in the project's lifecycle. This has also been proposed in Slack by @fila95 in...