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
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
Is there a particular reason that natalie.swift is placed outside PROJECT_DIR and the example project actually uses the natalie.swift located at /usr/local/bin as opposed to the included natalie.swift? If it's not on purpose let me know and I'll refactor
The text was updated successfully, but these errors were encountered:
@krzyzanowskim I really like the homebrew approach. What I think would be even neater though is to have natalie as a pod dependency so when people check out your app code and run pod install, all the required dependencies will be fetched. As for the Run Script Phase, an option would be to add it manually (using the Pods/natalie/natalie.swift file), or to let the cocoapods modify the app project when natalie is fetched.
Having to install natalie separately (even with homebrew) is an issue to me.
I see Natalie more like an external tool, like genstring, swiftlint... Your project is not really dependent on it
I create a symbolic link between my local project clone and /usr/local/bin (and use the xcode plugin)
Is there a particular reason that
natalie.swift
is placed outsidePROJECT_DIR
and the example project actually uses thenatalie.swift
located at/usr/local/bin
as opposed to the includednatalie.swift
? If it's not on purpose let me know and I'll refactorThe text was updated successfully, but these errors were encountered: