Oct 07 2017 14:39Eric Marchand updated
- Mar 18 2017 08:37sutao commentedContinous Integration(TravisCI, appveyor), Coverage(Codecov,)
Could we add a read operator, like we have a write one
maybe something like that :
|>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
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?
it's a little weird that fork have so many stars... a fork just to make new release
maybe a lot of chinese :p https://twitter.com/search?q=filekit%20Dschee&src=typd
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
I definitely do want to clean it up and introduce Swift 3 compatibility
@Dschee Are you interested in becoming an active maintainer?
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.
@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.
Deploying is pretty straightforward since I do it pretty much right after making a new tag and pushing
Thoughts?