Julian Paas
@NSManaged var gamePlayerStats: [PlayerStats]
class func gamePlayerStatsItemClass() -> PlayerStats.Type { return PlayerStats.self }
Jens Alfke
> On Sep 15, 2014, at 1:43 PM, Julian Paas <julia...@osaaru.com> wrote:
>
> @NSManaged var gamePlayerStats: [PlayerStats]
I haven't gotten into Swift programming yet — is the "@NSManaged" declaration equivalent to "@dynamic" in Objective-C? (It needs to be, otherwise CBLModel won't recognize gamePlayerStats as a database-backed property.)
> class func gamePlayerStatsItemClass() -> PlayerStats.Type {
> return PlayerStats.self
> }
—Jens
Julian Paas
class PlayerStats : NSObject, CBLJSONEncoding { required init(JSON jsonObject: AnyObject!) {
... }
func encodeAsJSON() -> AnyObject! {
.... }
}It took me quite a while to figure out how to return a class in Swift. Since I was only about 80% sure that gamePlayerStatsItemClass method is correct, I just tested it by creating an objective-C class with a method that would call gamePlayerStatsItemClass so I could see what the response looks like on the Objective-C side. As far as I can tell, it works. It returns a class with a module namespace prefix. i.e. the class is named "mymodule.PlayerStats". So the method signature does appear to return an objective-C Class.
Jens Alfke
Julian Paas
Jens Alfke
On Sep 16, 2014, at 7:04 AM, Julian Paas <julia...@osaaru.com> wrote:Have there been any thoughts/discussions about a native Swift API?
Julian Paas
Karel-Jan Van Haute
Julian Paas
class Team: CBLModel {
@NSManaged var name: String
@NSManaged var type: String
class func teamsByName() -> CBLQuery {
let query = databaseMain.viewNamed(kCblViewTeamsByName).createQuery()
return query
}
// Because class variables are not supported yet.
class func typeName() -> String {
return "Team"
}
override func willSave(changedPropertyNames: NSSet!) {
self.setValue(Team.typeName(), ofProperty: "type")
}
}
Julian Paas
import Foundation
class ArrayItem : NSObject, CBLJSONEncoding {
let holding: Int
init(holding: Int) {
self.holding = holding
}
required init(JSON jsonObject: AnyObject!) {
self.holding = 0
}
func encodeAsJSON() -> AnyObject! {
return ["holding": self.holding]
}
}
class TestModel : CBLModel {
@NSManaged var itemArray: [ArrayItem]
@NSManaged var simpleArray: [Int]
class func all() -> CBLQuery {
let query = databaseMain.viewNamed("allTestModels").createQuery()
return query
}
class func itemArrayItemClass() -> AnyClass {
return ArrayItem.self
}
convenience init() {
self.init(newDocumentInDatabase: databaseMain)
itemArray = [ArrayItem]()
simpleArray = [Int]()
type = "TestModel"
}
}
That declares the model object. Here is an example that will look up the objects and try to access the properties. When it tries to access the property named itemArray, it causes a fatal error.
func runModelTests() {
var error: NSError?
let queryEnumerator = TestModel.all().run(&error)
assert(error == nil, "Unable to query all TestModels")
while let row = queryEnumerator.nextRow() {
let testModel = TestModel(forDocument: row.document) as TestModel
println("properties: \(testModel.document.properties)")
println("simpleArray: \(testModel.simpleArray)")
// Here's where we access the array of objects and get...
// fatal error: NSArray element failed to match the Swift Array Element type
println("itemArray: \(testModel.itemArray)")
testModel.deleteDocument(&error)
assert(error == nil, "Unable to delete TestModel")
}
let testModel = TestModel()
testModel.simpleArray.append(0)
testModel.simpleArray.append(1)
testModel.itemArray.append(ArrayItem(holding: 10))
testModel.itemArray.append(ArrayItem(holding: 11))
testModel.save(&error)
assert(error == nil, "Unable to create test model")
println("Created TestModel: \(testModel.document.properties)")
}
Jens Alfke
adam wilson
Or do the model classes still need to be Objective-C?
Julian Paas
Jens Alfke
On Sep 15, 2015, at 3:30 PM, adam wilson <adam.el...@gmail.com> wrote:
Has there been any progress on this? I'm in the process of building an iOS CBLite app with Swift and hit this issue with CBLModel and @dynamic properties...