Questions to contribute about sugarrecord

[pepicrft]

Hello @fjbelchi , answering:

1. Yes, Travis-CI doesn't support XCode 6 yet so unless any of us has a XCode server to make these builds it's going to be impossible to have it automated. I don't know which are the plans of Travis-CI regarding the integration with XCode 6 but with XCode 5 they took a lot of time. I would ensure the tests are passing before merging any PR. Otherwise if you know any better option let me know.
2. I have it planned. I started developing it following as an example not only MagicalRecord but the implementation of AlamoFire (by Matt) where he uses only one file but I agree with you, it's clever to have them in different swift files. I've added it to pending stuff.
3. With code convention you mean patterns?, I've tried to follow an style-guide made for swift but we can talk about it :)
4. Not bad idea. Creating it!
5. I agree with you in this point. Think it has to be as sugar as possible but IMO this will be something that will bring out as soon as we start reading more code in Swift and specially other implementations and patters. Feel free to add your own ideas. BTW, I love ObjectiveSugar, it's so Ruby

[pepicrft]

Done @fjbelchi https://github.com/SugarRecord

[fjbelchi]

Cool, I've changed the upstream :)

1.) I'll try to find out others alternatives to Travis-CI or possible works around. I guess probably Travis-CI maybe wait until xcode6 is out of beta.

2.) and 3.) It will be amazing if you could create the classes or describe how would you like to do it with the architecture you would like to follow. In MR is very clear where everything should be done.
When in the point 3 I said code conventions I meant the style guide, for example, having an extension of NSManagedObject, where should it go? - Without a name like the old categories, I haven't seen what the folk is doing to create an extension in separate files. Should it be like old categories, like that NSManagedObject+Find.swift ??

5.) what is your opinion about syntax like this:

let peopleInCurrentPage = db.people
        .filterBy(predicateFormat: "department IN %@", argumentArray: [[dept1, dept2]])
        .skip(pageNumber * itemsPerPage)
        .take(itemsPerPage)
        .sortBy("firstName,lastName")

let peopleSorted = db.people.orderByDescending("lastName").orderBy("firstName")

I've seen it here: https://github.com/Alecrim/AlecrimCoreData and it looks very fluent :)

[pepicrft]

Hello @fjbelchi

1. I think we should wait for Travis-CI giving support to XCode 6

2. Regarding your question about the naming, I'm going to add the styleguide I'm using, moreover I've separated the file into different files and folders to make it cleaner and easier to understand. As you say I've followed the old categories naming. I think ( IMO ) that Apple should keep that naming for extensions too.

3. I love that syntax, we could go around it and bring these concepts getting inspiration from other Swift libraries like the one you mention. Would you like to create an issue for that or do you know any platform to keep a forum or something similar to keep this kind of conversations that are not issues.

Thanks a lot @fjbelchi , I'm going to add you as a contributor!

[pepicrft]

Closing this @fjbelchi