Update kept to work with the new daybed.js

[almet]

This uses the new daybed.js API and works with kept to share the dashboards, using a hash in the url.

[leplatrem]

Isn't this operation idempotent ?

[almet]

It is, yes, but I don't understand what's the matter here?

[leplatrem]

Why do you compare the current value then ?

[almet]

This says: "If the current session is different from the one of the hash, then set the hash to the new value".

[leplatrem]

I mean : what's the problem with overwriting with the same value ?

[almet]

Ah, I prefer avoid doing so as I don't know what that triggers for the browser (e.g. if there is no need to, why should we update it?)

[leplatrem]

Ok, no problem dude ! Just FYI onhashchange is called only if the value changes :)

[leplatrem]

I don't get this : each user will have its own model ?

[almet]

Each token, yes.

[leplatrem]

Can you explicit pros and cons of this pattern please ? Maybe in Daybed documentation page about permissions ?

( only one I can foresee is about managing permissions, but TBH I find it weird )

[almet]

@n1k0 do you know if the failures are due to the daybed.js changes or aren't related?

[leplatrem]

We might have to choose a way to indent then() consistently...
I think I prefer this way:

return Daybed.startSession(self._options.host, {
    token: this._options.token
  })
  .then(function(session) {
    // ...
  });