You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of our projects use NStack together with its subdependency, LocalizationsManager. However, some projects need to be able to use LocalizationsManager without using NStack.
The current solution, where LocalizationsManager is a separate framework in a separate repo makes it hard to work on NStackSDK and makes it hard to support different dependency managers. According to Chris, it's kind of expected of NStack to use the same dependency manager as the projects that import NStack.
Let's see if we can have LocalizationsManager in the same repo and have the dependency managers we support for NStack (in order of desired priority: SPM, CocoaPods, Carthage) build and expose 2 frameworks from the same repo. Try and get some inspiration from Firebase, if possible
The text was updated successfully, but these errors were encountered:
Most of our projects use NStack together with its subdependency, LocalizationsManager. However, some projects need to be able to use LocalizationsManager without using NStack.
The current solution, where LocalizationsManager is a separate framework in a separate repo makes it hard to work on NStackSDK and makes it hard to support different dependency managers. According to Chris, it's kind of expected of NStack to use the same dependency manager as the projects that import NStack.
Let's see if we can have LocalizationsManager in the same repo and have the dependency managers we support for NStack (in order of desired priority: SPM, CocoaPods, Carthage) build and expose 2 frameworks from the same repo. Try and get some inspiration from Firebase, if possible
The text was updated successfully, but these errors were encountered: