Swift is evolving, and [SE-0386](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0386-package-access-modifier.md) introduced **the package access modifier** for more granular control in Swift packages. While it seems designed for Swift Package Manager (**SPM**), limiting access within a package, it's not exclusive to it. Even projects using **CocoaPods** can benefit from it!
A lot of time has passed since the release of the first version of Rugby. [Last time](/en/2021-03-09-rugby-story/) I struggled with indexing at all costs. This time, I was fixing fundamental problems and got a little carried away. This is how 🏈 [Rugby: Remastered](https://github.com/swiftyfinch/Rugby) appeared.
Do you have problems while working on a huge project with a large number of pods in **Xcode**? Maybe endless indexing? **Xcode** is always freezing during navigation through a project or while editing it? Slow rebuilding pods targets which have been already built recently?
In the [last part](/en/2020-06-06-cozy-pod-install-3) I mentioned about one new idea 💡. Recently, I needed to sort out the order of bumping **CocoaPods** dependencies in a working project. In this post, I will describe how you can do it using **Ruby**.
In the [last part](/en/2020-05-31-cozy-pod-install-2), we wrote a small wrapper over the regular **CocoaPods** and figure out how to skip unnecessary calls. In this part, let's try to automate a couple of interesting cases. The main goal is to run the **pods install** command and switch to other tasks while it is running.
In [last part](/en/2020-05-23-cozy-pod-install), we cut down the **bundle exec pod install** command to **pods install**. Just one letter more than the usual ** pod install**. And this time let's see what other upset moments happen while using this command.
In this post, I will describe how you can ✨ enhance your work with **CocoaPods** in the terminal. I often have to use **CocoaPods** in my work, and even more often I open a terminal and write there **pod install**.
I think many iOS developers have worked with escaping **URL**. But can you instantly answer does **JSON** escapes when it sending to **body**? In my work, I faced the fact that by default the **JSON** **body** of the query is escaped when using the standard **JSONEncoder**. So you can ask what is wrong with this?