Clarify that etags are required for the remote persister about tinybase

[jamesgpearce]

Done. Thanks!

[jamesgpearce]

Thanks! You should definitely expect this to work!

Do you have React StrictMode on? I just fixed a problem that had that symptom in yesterday's release.

A few other questions:

• is myOwnCreateRemotePersisterFunction doing anything unusual?
• does it update if you call an explicit .load() ?
• can you see whether the underlying Store has in fact been updated? (maybe just debug a store.getJSON() to look), in which case it will be a rendering thing

[bndkt]

Thank you @jamesgpearce, that sent me down the right path, and I found the problem.

I'm not using strict mode, but calling an explicit load via a setTimeout yielded the desired result, so it must've been the autoloading code. And then I looked at the code more closely and saw that the listener is checking for an ETag in the HTTP-response (

tinybase/src/persisters/persister-remote.ts

Lines 41 to 48 in 3203b84

	if (
	!isUndefined(lastEtag) &&
	!isUndefined(currentEtag) &&
	currentEtag != lastEtag
	) {
	lastEtag = currentEtag;
	listener();
	}

) and wasn't sending one. As soon as I added an ETag to the server, it started working. Probably worth mentioning that in the docs for the remote persister. I'm happy to put a notice in there, unless this was unintentional but the code looks like you want it to only work with ETags and it also makes sense I think.

[jamesgpearce]

Hm, that's a good point. I think I am way too implicit about that. Thanks for the debug and suggestion!