プチ Reviews 2.0 Update #5
FixesArray.at method
Looks like backend doesn’t really check how many times an update for a review was sent. @veritas_nz probably you need to check if review is updated after next_review time, and if next_review time didn’t happen yet, don’t update a review item.
If I accidentally close my browser during a review session and then open it again, I see the same reviews I already answered. If I answer them again, it bumps their SRS level again. Just a half an hour ago I bumped two ghosts from SRS3 to SRS4, now I answered them once again after reopening my browser. UI shows like I bumped them from SRS3 to SRS4 again, but this response from Bunpro suggests I actually slayed them:
So there should be added some sanity check I guess.
And this is how it looks like in the session summary.
The same vocab appeared twice.
And the second sentence didn’t appeared in my session, I actually answered the first one twice.
Does this happen only with Ghost Reviews?
session_id
session_id
was_correct set to falseNot exactly sure I understand the issue, as I’m not able to replicate it!
Any further info would be much appreciated 
You’re thinking about another known issue, but this isn’t that one.
One important point that browser will open the /reviews page completely from the cache without making any new network requests. As it was loaded before. So correctly answered questions would actually reappear because the page was loaded from cache as it was loaded from the server before the browser was closed.
If I would hit Ctrl+F5 correctly answered questions would indeed disappear, but I’m not sure all Bunpro users are so tech-savvy to make sure they purged their cache.
That happens because /reviews page always have the same ETag, so browser may show the page from the user’s cache. Your Cache-Control header suggests that browser must revalidate the page, but ETag happens to be the same. So browser just shows the page from cache. And all API requests are loaded from cache as well but without revalidating them. So all reviews reappears, because /api/frontend/reviews is loaded from cache too.
And if I answer the same review again, its SRS level bumps twice.
You could fix the issue by adding no-store directive to Cache-Control header on the api/frontend/reviews endpoint and removing ETag from there to make sure browser will never cache this API call, but it’d be nice also to add a sanity check to the /api/frontend/.../update endpoint. If user sends an update for a review before next_review time, then it’s obviously a cache issue. Just don’t update review in this case and return current review data.
プチ Reviews 2.0 Update #6
Summary ‘loading’ feature updateThis update basically just makes the Summary page load prettier.
No more is there just a big booty loading-spinner below the title.
Thanks to @bunnypro for all these suggestions!
Fix To-do List
/api/frontend/reviews route is never cached
Great, thanks for making the changes! 
Japanese sentences lack line breaks and gray name highlight on session summary screen.
English translations have them.
プチ Reviews 2.0 Update #7
Features FixesIf last review item in review is an early incorrectly answered vocab without example sentences (that requires to enter an English translation) and I enter an incorrect answer again, pressing Enter does nothing, just a short blink. I can’t submit an incorrect answer, only erase it by pressing Backspace.
Should be fixed!
Please let me know if this bug shows up again and thanks for the feedback!
Thank you!
One more minor issue: “Connection Error” dialog box could be closed by clicking outside of it, so unsubmitted review won’t be submitted at all. I guess this dialog box wasn’t meant to be closeable.
A wrong example sentences is shown in the last session summary for a newly added vocab.
Session ID 2790299.
Updated
@veritas_nz All my vocab reviews for recently added vocabs in Cloze mode are shifted by one. When I review vocab item, I see example sentence number i, but in the session summary it’s always sentence number i+1.
Earning XP for these vocabs also broken. I did reviews the second time and get 1 XP for each of them again instead of 2 XP.
One more minor issue: “Connection Error” dialog box could be closed by clicking outside of it, so unsubmitted review won’t be submitted at all. I guess this dialog box wasn’t meant to be closeable.
I could make it so that the user isn’t able to close the modal, but this would mean that if there is a review that is unable to be updated (i.e. if it’s bugged for whatever reason) this would mean that the user could not progress to another question
A wrong example sentences is shown in the last session summary for a newly added vocab
I believe it wasn’t just Vocab!
Should be fixed now though.
Earning XP for these vocabs also broken
Is this error still occuring? We were aware of the Summary page sentence bug, but the XP bug shouldn’t be happening!
Thank you for the fix!
Yes, now it works as expected. I earned 2 XP after reviewing a vocab the second time.
Yeah, this makes sense. Maybe it could be nice to add a X button to close it instead of clicking on the backdrop? Because it’s kinda easy to close it accidentally.
プチ Reviews 2.0 Update #8
Features FixesClosed!
If you have any more bugs to mention regarding this release, please post them to this topic
