Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Eric Marchand
@phimage
Could we add a read operator, like we have a write one |>
maybe something like that :
            prefix operator <| {}
            public prefix func <| <Data: DataType>(file: File<Data>) throws -> Data {
                return try file.read()
            }

            let dataFile = DataFile(path: .UserTemporary + "samplefile")
            let contents = try <|dataFile
Cihat Gündüz
@Dschee
Hi guys, can anybody tell me why my fork is getting so many stars the last few days? :D
Was there any blog entry or conference where somebody mention the fork? Can't find anything on twitter ... anyways, I'm happy the fork helps.
If the plan is to use the fork as the main repository then we probably should do some referential changes in the README and maybe also change the GitHub reference. We could create a FileKit organization for example and I could add some more people as the maintainers. What do you think?
Eric Marchand
@phimage
it's a little weird that fork have so many stars... a fork just to make new release
Eric Marchand
@phimage
Organization is not necessary, I think it's useful for big project or many related projects. I am a project maintainer, but I am not registered to CocoaPod to make new release. Only project owner have the right to do it.
Nikolai Vazquez
@nvzqz
The main repo has also been getting a lot of traffic lately
And I'm not sure why
I wrote release notes for a version 3.0 of FileKit but I've been occupied with Sage although now that it's at 2.0 I'll spend more time on this
Creating a FileKit organization could be a possibility
@phimage what do you think?
oh wait nevermind
Nikolai Vazquez
@nvzqz
My main problem with FileKit right now is that I haven't touched it in so long and it's grown to be larger than I've anticipated at 4000 LOC
I definitely do want to clean it up and introduce Swift 3 compatibility
@Dschee Are you interested in becoming an active maintainer?
Cihat Gündüz
@Dschee
I found the source by checking the traffic: Some people seem to have interpreted my CocoaPods release as a new software and think that I was the one writing the library (although I didn't change any of the author entries) – see https://iosdevweekly.com as an example.
Nikolai Vazquez
@nvzqz
Huh. Well at least it'll get more people to use it which isn't bad
Cihat Gündüz
@Dschee
@nvzqz Sure, I'd love to help maintain FileKit. But that won't solve the issue with deploying a new version as @phimage already said. I'm not sure what to do from here since both libraries seem to have quite some stars now – we should definitely get all people onto one place, but for now I think it's okay to wait for you to get the 3.0 release done as you already mentioned in the post and keep things as is. I can then add a hint to the README that the software is deprecated and they should use the original project instead. Okay this way? Should be the least-work solution.
Nikolai Vazquez
@nvzqz
For now people have a version to use with the latest changes on your fork but sure when I release 3.0 then you can note that all active development is in the parent repo
Deploying is pretty straightforward since I do it pretty much right after making a new tag and pushing
Cihat Gündüz
@Dschee
Okay then, let's do it like that. :-)
Nikolai Vazquez
@nvzqz
I'm thinking having 3.0 as a version with all the latest changes but then 4.0 as a swift 3 compatible version that's been cleaned up a bit
Thoughts?
Cihat Gündüz
@Dschee
Are there any breaking changes since 2.0?
Nikolai Vazquez
@nvzqz
A few such as renames
Cihat Gündüz
@Dschee
Well then, a 3.0 release seems a reasonable choice as far as I'm concerned
And adding another one once Swift 3 is out with some streamlining in 4.0 would be great, too of course
Nikolai Vazquez
@nvzqz
Since a lot of people are jumping on xcode 8 and swift 3, is backwards compatibility with swift 2 that important?
It makes the code harder to maintain since some things need to be separated. Sage is swift 2 and 3 compatible for example
Cihat Gündüz
@Dschee
I would simply drop Swift 2 support but that's also your choice to make
But not now, of course since there's a few weeks or months until official Swift 3 release
Nikolai Vazquez
@nvzqz
Two weeks I believe until there are no more breaking changes to swift 3 and they start discussion for swift 4