From d860ab0ae040d541b732430f79b3a72379d0a41a Mon Sep 17 00:00:00 2001 From: Stein Magnus Jodal Date: Mon, 3 Dec 2012 23:02:24 +0100 Subject: [PATCH] js: Document behavior on calls when we're offline --- mopidy/frontends/http/__init__.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/mopidy/frontends/http/__init__.py b/mopidy/frontends/http/__init__.py index 4fa48c79..7f8db3b2 100644 --- a/mopidy/frontends/http/__init__.py +++ b/mopidy/frontends/http/__init__.py @@ -224,6 +224,10 @@ Once your Mopidy.js object has connected to the Mopidy server and emits the mopidy.playback.next(); }); +Any calls you make before the ``state:online`` event is emitted will fail. If +you've hooked up an errback (more on that a bit later) to the promise returned +from the call, the errback will be called with an error message. + All methods in Mopidy's :ref:`core-api` is available via Mopidy.js. The core API attributes is *not* available, but that shouldn't be a problem as we've added (undocumented) getters and setters for all of them, so you can access the