People are willing to contribute to open-source projects, but many issues are not beginner-friendly.
I am happily surprised that @tuistio has 20 open issues labeled as "good first issue" on GitHub. Over half of them were opened in the last twelve months. 👏
We have released a new version 3.4.0 Feuerwehr 🔥
📦Support for automatic resources in SPM
⌚️ WatchOS UI test targets
☁️ Sending cache targets hits analytics metadata
And more ✨
Check out the full changelog here: https://t.co/8kURxTPioM
Hey Twitter. Could you recommend a wireless charger that allows to charge iPhone, watch and AirPods at the same time? Those from Apple site are very expensive so before buying a one I want to find if there are other alternatives. 🤔🤔🤔
I learn a lot of new vocabulary when I’m reading books or watching videos with subtitles. I’m looking for an app that allows me to build glossaries after every movie/book. Could you recommend something?
@simonbs Currently: APIClient / APIClientProtocol / APIClientProtocolMock but it always depends on a project or team arrangements. I don't have a golden rule for this naming. I have been working with a few approaches. In Tuist we have: APIClient / APIClienting / MockAPIClient.
@simonbs@tuistio@marekfort@danyf90@simonbs BTW. maybe you don't need SPM for local modules. You could try to define your local modules (packages) using primitive types of tuist.
@simonbs@tuistio It should be deprecated for external packages only. There is on other way for adding local packages. We will try to fix this deprecation or describe a new way for adding local packages.🤞 CC @marekfort@danyf90
@simonbs@tuistio When you add your package to "Project.packages" then you will be able to add products from the package to a target via "Target.dependencies.package(product: <Name>)".
@simonbs@tuistio Add your package using "Project.packages" property. "Dependencies.swift" and ".external(“Onboarding”)" are reserved for external dependencies only.