André J

The reason we use .framework is so that you don't have to compile all the files on every run. This library is meant more as a pick and choose lib....

I break out libs on a need by need basis. If you want to use the Constaint lib. You need Constraint.swift, Alignment.swift and ConstraintKind.swift. FYI: the constraint lib wil get...

There are no stupid questions 😉. I USE the latest swift version so that should be 4.2. I just upgraded to Mojave so im not 100%

AS far AS i know there ahould not be huge differences in warnings between 4.1 and 4.2 i will give it a spin at the office today in Mojave. I’m...

@kimasendorf Alrighty, here we go. 4.2 🔸 I tested it in Mojave + Xcode 10.0 + swift 4.2 all tests run. https://github.com/eonist/swift-utils/commit/395e8b83575821efbd53736172f06e344d609da3

I will try to Add the code to a new project and see if there stil are bugs. Also I will make an on boarding wiki page with some gifs...

@kimasendorf Updated the files that threw an error and made better on boarding for using the lib, http://eon.codes/blog/2018/09/30/Manually-adding-a-lib/ Will update the build from framework article with gifs later today.

@kimasendorf As promised, I added gif videos the explains the steps to build from a framework file: http://eon.codes/blog/2017/11/08/local-frameworks/ in your case you would just need to name the target Utils...

If you do the steps in the local framwork article exactly AS they are sone in the GIFs it should work. This is how you would menes any framework, not...

Notice that you have to prefix import with @testable. You also need reach the correct class/instance scope . I.e ArrayParser.count([7,9,7]) //output:3