Release 1.7

[andrewimm]

Planned changelog:

• Store server data and pending ops on-object when single instance mode is disabled. This will prevent memory leaks. (structural change only, does not affect APIs or behavior)
• Default to setting A+ Compliance to true. See Proposal: The future of Parse.Promise #57 for more details. (landed in 96e211d)
• Enable native-style construction of Parse.Promise. See Proposal: The future of Parse.Promise #57 for more details. (landed in 5e5c444)
• Re-commit Make sure when argument corresponds with then arguments #115, changing the behavior of Parse.Promise.when(). The response provided to the asynchronous callback will match the style of its arguments. (landed in 7da2856)
• Add revert() instance method to ParseObject (landed in 7c16dee)

When these changes have all been committed to master, and end-to-end tested, we'll release 1.7.0

[TylerBrock]

This would be great. Thanks Andrew

[grantland]

I ❤️ #115

[mohnazemi]

Changelogs were not updated for the last several releases on the Downloads page. Is there a reason ?

[andrewimm]

@mohnazemi the source of truth for changelogs will always be here on this repo: https://github.com/ParsePlatform/Parse-SDK-JS/releases

I'll update the downloads page to include the last few releases

[srameshr]

@andrewimm Caching built into the JS SDK would be a very useful addition. App's built for the webview in IOS and Android platform would have a huge boost. In the docs you clearly say don't use REST API when you have native sdk for your platform.

[andrewimm]

@srameshr we are working out a number of strategies for caching, but it will not be an official feature until at least 1.8. It will most likely end up being a plug-in that can be added to the SDK, rather than a change to the SDK itself.

[srameshr]

Any particular date on which, this would be available?

[andrewimm]

@srameshr As a rule, we don't commit to dates for releases. Even less so for features where we're still unsure what to implement.

As it is, it's trivial to implement your own cache in your own application. This is a simple implementation of one:

updateCache(object) {
  let identifier = object.className + ':' object.id;
  let currentCache = JSON.parse(localStorage.get('cachedObjects') || '{}');
  currentCache[identifier] = true;
  // Store object to localStorage
  localStorage.set(identifier, JSON.stringify(object._toFullJSON()));
  // Store updated object index to localStorage
  localStorage.set('cachedObjects', JSON.stringify(currentCache));
}

getCachedObjects() {
  let objects = {};
  let currentCache = JSON.parse(localStorage.get('cachedObjects') || '{}');
  for (let identifier in currentCache) {
    let objectString = localStorage.get(identifier);
    if (objectString) {
      try {
        objects[identifier] = Parse.Object.fromJSON(JSON.parse(objectString));
      } catch (e) { }
    }
  }
  return objects;
}

[srameshr]

I am doing something similar to this ...

[jmornar]

@andrewimm Although I know you are not commiting to dates, I have to ask do you have at least a rough estimation of when version 1.7 with memory leak (when running in server environment) fix could be released? just to know if it worth to wait or we have to look for a new solution as we already have this issue on production for some time now?

[andrewimm]

I'm aiming to get something out this week -- the changes involved are pretty significant, but I'm about 2/3 of the way through. In the meantime, I've posted a number of potential workaround ideas in other threads related to the issue.