Due to how JS interprets 0 as falsy, the Sqlite driver's maxLocalIndex property would regress to -1 when it should actually be 0. This could result in being unable to write more than one document to a replica. I hope this is the fix to #240.
Tests didn't catch this because the Sqlite test scenario was marked as persistent: false. I fixed that up.
I also made it so that drivers validate share addresses. If you'd create a driver with a bad share address, it would still get to the point where it'd persist that bad share address to a file on disk.
Due to how JS interprets
0
as falsy, the Sqlite driver'smaxLocalIndex
property would regress to-1
when it should actually be0
. This could result in being unable to write more than one document to a replica. I hope this is the fix to #240.Tests didn't catch this because the Sqlite test scenario was marked as
persistent: false
. I fixed that up.I also made it so that drivers validate share addresses. If you'd create a driver with a bad share address, it would still get to the point where it'd persist that bad share address to a file on disk.