-
Notifications
You must be signed in to change notification settings - Fork 37
Knockback compatibility #34
Comments
OK, I finally figured out what "Nested data can be provided through the source property in a model's attributes" means in practice. It restores the attribute and clears the collection returned by the association function. But what does that mean exactly? Does that mean that by using |
Hi @neverfox! The |
Hi @braddunbar. I see. Thanks. I had a long set of questions here before but, after playing around, I think I see how it all works now. What I wasn't understanding before was that JSON for a List model like |
So what do you typically do when you want to save models back to the server? Because the JSON gets pulled apart by supermodel, |
@neverfox you could overwrite the |
First of all, supermodel is a really elegant library. I was hoping it would help take the place of backbone-relational in a knockback app I'm working on. However, because "nested data is used and removed with model.parse," it creates some difficulties. That's unfortunate when other libraries assume those nested collections will be attributes but perhaps that's the only way to achieve what supermodel is trying to achieve and there's no way around it.
Knockback does apparently have the ability to get pretty fancy with customizing how things get constructed in a kb.ViewModel so perhaps a workaround is possible. Does anyone have any experience making these libraries work together?
The text was updated successfully, but these errors were encountered: