Questions about bug fixing process and support licenses

Questions about bug fixing process and support licenses

We are currently evaluating Sencha Touch as a platform to move forward with and I've been playing around getting a feel for it's capabilities.

We are pretty keen on what we have seen and will likely purchase a support license, however this duplicate problem caused me some grey hairs, so I have some questions I hope can be answered:

Is this a bug or have I set up things incorrectly?

If this is a bug is it fixed in the version available only to support licensees? Is there any public information about what is in the version available only to support licensees?

If this bug is not fixed in the version available to support licensees then what would be the normal turnaround for such a bug fix to become available (if we had a support license)?

I notice that in this post you mention "If we get demand for a github repository featuring just the public releases we may set that up too" - can I add a vote for that? It seems that would make submitting fixes like this easier for both sides if we could generate pull requests on github.

I noticed this issue too

Basically, when the DataReader reads a response back from server, it instantiates new record instances, with new internalId set.

When the store has its onWrite callback fired, it tries to replace the original record (which caused the CREATE/UPDATE action) with the new version from server, but it can't possibly find it unless their internalId are set the same.

This is a recurring issue with the architecture around creating Model instances locally and saving them remotely. At the moment it's rather difficult to accurately match each record returned by the server against the record we sent to the server.

We're formulating a better solution to this internally at the moment and will keep you updated.