Open alexander-alvarez opened 7 years ago
Now that is an interesting idea .. I must say. Don't think it would be hard, just take a few days because it requires alot of new tests. You want to try for a PR, or you want me to try it?
How does the buffered apply to auto tracking? Maybe there could be another option to buffer when tracking.
Also there is an open issue in that buffered-proxy for handing belongsTo and hasMany .. so this would actually not work unless I could figure out how to make that work.
I could take a stab at it if you're not opposed to the API, it will likely take me a bit longer though
How does the buffered apply to auto tracking? Maybe there could be another option to buffer when tracking.
you could probably configure it as you do auto.
Also there is an open issue in that buffered-proxy for handing belongsTo and hasMany .. so this would actually not work unless I could figure out how to make that work
I'm not sure what you're referring to here
https://github.com/yapplabs/ember-buffered-proxy/issues/7
Let me give this a try and I will probably find out the issue they are dealing with.
Also, you could just use buffered proxy for change tracking too right?
It is almost as if that concept eliminates the need for change tracker on the ember-data model, since your doing it on a proxy.
I was perusing that earlier, not sure I see any blockers to what we need to do. I'll share any progress I make as I make it.
But I am asking you .. could you use the buffered proxy right now to do change tracking and rollback on an ember-data model? I am guessing you can not since it does not handle relationships?
Would you be open to having a buffered mode? / how hard would it be to leverage the same tracking mechanism you have but in addition to:
we could also do:
a la https://github.com/yapplabs/ember-buffered-proxy