Kamil Harasimowicz

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. 👏

@simonbs @tuistio Yes, it requires to be setup with Tuist. :/

@laxmorek @tuistio Interesting! But that requires my project to be setup with Tuist, right? I’m thinking it should be possible to generate this graph without any manifest file.

Does anyone know a tool that can draw a graph of the relationship between local Swift packages in a project? It should build the graph based on the .xcodeproj and Package.swift files. `swift package show-dependencies` can do it for packages but I need it for an Xcode project.

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: github.com/tuist/tuist/re…

@tuistio popularizing Tuist during the Kazakhstani iOS Developers Meetup! Thanks for your amazing work! cc @PinemelonMarket

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. 🤔🤔🤔

Two new books on my virtual shelf. @rwenderlich

@hnilsen 🎂🎂🎂

Fjortis! #MyTwitterAnniversary

@tuistio is able to speed up your CI dramatically! Give it a try!

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.

How do you name your Swift types when heavily using protocols? For example, if you need to create an API client that conforms to a protocol and only the protocol is exposed publicly. APIClient and APIClientImpl? APIClientProtocol and APIClient? Something else?

@pepicrft Kudos to @marekfort I've just used what he prepared.

`tuist-plugin-lint` v0.3.0 has been released! 🎉github.com/tuist/tuist-pl…

@danyf90 @simonbs @tuistio @marekfort For caching I strongly recommend a video that was recorded by @pepicrft youtu.be/Qq7E3YlPJog

@danyf90 @simonbs @tuistio @marekfort That was my point. The only way to achieve what @simonbs needs is the deprecated way. You can't use Dependencies.swift for that.

Does anyone know how to add a local Swift package to an Xcode project using @tuistio? Currently using Dependencies.swift and adding .external(“Onboarding”) and .external(“Overview”) to my list of dependencies. It looks like it’s setting up old fashioned frameworks though 😕

@simonbs @tuistio @marekfort @danyf90 Sure, it sounds reasonable. You have to be aware that Tuist cache mechanism will not work for local Swift Packages.

@laxmorek @tuistio @marekfort @danyf90 I’d really prefer to use Swift Packages. I like Tuist but I’m not ready to go all-in on it, so I’d like to keep some aspects a bit “vanilla” 😊

@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.