Now that the kinto-http-client has shipped, we can take advantage of it instead of using raw fetch() calls to fetch the changes from Kinto. This would imply splitting the `PREF_KINTO_CHANGES_PATH` pref that contains a piece of URL into two prefs: * changes bucket name * changes collection name This way we would do: const client = new KintoClient(SERVER_URL); client.bucket(BUCKET_ID).collection(COLLECTION_ID) .listRecords() .then(result => ...);
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.