Marek Fořt
Marek Fořt
> I am leaning more towards Kas proposal of making the warnings more visible I think this should be the first step - but still, having something akin to the...
> If we do it in Config.swift, we could allow passing of a closure which takes a warning and returns whether the warning should be ignored, be printed, or abort....
> Doesn't Config need to be "static" (i.e. how would you generate the JSON to parse it)? That is true, `Config` needs to conform to `Codable`. However, such a feature...
Reopening as we are reconsidering this and even with warnings at the end of the generation, the `--strict` flag may be useful, especially on the CI.
> I've rebased and made some fixes. Still have no idea what's happening on CI tho. All tests pass fine locally. `main` seems to be green the couple of last...
> when can we expect to see this bugfix in release and which version? We try to release weekly on Monday, i.e., there should be `4.14.0` tuist release on Monday.
Have you had time to look at this? I'd love to use this for my own tooling and I think it'd be a great addition!
Yeah, I wanted it for Swift packages; I'll see if I have the time, thanks for the intro to this issue :)
SwiftUI template is the new default, the UIKit one is gone. You don't need to specify the template when using tuist init. Wanna contribute to them docs? 😁
Hey 👋 I just downloaded tuist from brew, but can't reproduce the issue. Can you check the following: > Does running `/opt/homebrew/Caskroom/tuist/4.8.1/tuist init` work? > What do you see when...