Open cclauss opened 3 weeks ago
This project has numerous Package.swift files but none at the root of the project.
Most of these regard Homebrew packages. The actual Package.swift
is this one: https://github.com/buresdv/Cork/blob/main.swiftlint/Tuist/Package.swift
Keep in mind though that this Package.swift
is managed by Tuist, so I'm not sure to what extent it is a "vanilla" Package.swift
.
I know very little about either packages or the Swift CLI, so I'd keep the specifics to you
Hey, I don't want to rush you :) Have you had a chance to look at this more?
Suggestion type
The way Cork works
What is your idea about?
378 runs
swift build
andswift test
but they currently fail looking for aPackage.swift
file.This project has numerous
Package.swift
files but none at the root of the project.What is the best way to run
swift build
andswift test
? Should wecd
into each directory and run these commands or is there a way to create a project-widePackage.swift
that allows the building and testing of all files?Why should this be added?
Automated testing helps us find bugs in new code submissions before manual code review.
Keeping it real