Closed yoann-antoviaque closed 10 years ago
Sorry, but it looks like the tests do not pass, so I won't merge :(
which tests do not pass ?
I have a test maked as failed on Chrome ("Use AjaxSync when no database is specified") and a "global failure" in firefox on the unpatched version...
The two tests using keypath on the patched version are ok while failed on the base revision (when keypath is not "id")
I'm willing to help but as tests seem to fail on your own code on an unrelated test case I do not understand... If I missed something or your results are not the same, I would be glad to fix some issue with my modification but cann't see it...
The travis tests don't pass in here pull request while they do in master.
could you be more specific about which tests do not pass ?
I'm executing tests/tests.html in chrome and firefox and here are the results:
head revision from your repo on chrome: on firefox:
first revision on my pull request (modified tests with keypath != 'id', untouched backbone-indexeddb.js) on chrome: on firefox:
head revision on my pull request on chrome: on firefox:
from my view you have few tests that do not pass depending on the browser (support for the 'addIndividually' property and use ajaxsync when no database is specified on chrome, create duplicate models on firefox) on the head revision, those still fail with my patched version but no other test fails... what am I missing ?
Yoann, as you see we use Travis on this repo. The master branch passes the test as indicated by Your PR does not build on the other as indicated by
I am really sorry I don't have time to dig further at this point. If you make the Travis tests to pass, the, I'll happily trust and merge.
Hi! As you asked here is a pull request fixing the issue I raised.
while writing the test I realized that you used the standard "id" field in your keypath, it was the reason you have not experienced such problems. I changed it to "keyPathId" for the Torrent model, such change raised quite the same error in fetch, therefore I fixed it :)