This is a third-party script/app and is not created by the WaniKani team. By using this, you understand that it can stop working at any time or be discontinued indefinitely.
Dashboard Level Progress Detail once again is not being maintained, so I have adopted the script. This is an update to that script.
v1.0.5: Fix the bug fix because I’m blind (thanks @rwesterhof yet again) (2021-04-06)
v1.0.4: Bug fix for max level users (thanks @rwesterhof again) (2021-04-06)
v1.0.3: Re-render if cache has changed (2020-10-05)
v1.0.2: Official setting for requiring 100% learned and the halfway marker, fixes location bug (2020-09-26)
v1.0.1: Official setting for border radius and hiding current level items (2020-09-25)
v1.0.0: Initial release - Breeze Dark support, constants, round progress (is also a constant), halfway marker, and settings for what progress to show! Now works with new dashboard (thanks to @rwesterhof) (2020-09-25)
History of how this script got here (this part has nothing to do with me):
Thanks for updating this! I really love the old Dashboard Level Progress Detail script. I was able to change the bar radius constant to 0px in yours to bring it back to the old style of just bars, rather than bubbles (no offense to the new style, it’s cool too).
One thing I spent a few hours fiddling around with the old script to do was keep the default WK level progress section and have the script append the progress bars at the end. I did it in a really weird hacky way since I know nothing about WKOF or js in general, but it worked to let me display my dashboard like this, without having those progress bars appear twice (which happened if I just removed the empty() line)
Is there any chance that this could be a built in feature within the settings menu to not fully empty out the progress section and instead show the progress bars in addition to the base level progress? I like to be able to see all of the individual items for the current level, but be able to get a glance at the progress (especially for vocab) of the previous and current level items.
So awesome!! I just decided to look to see if there was something that would show my lingering vocabulary items and I found this right away - love it, love it, love it!! Thanks for grabbing and running with this.
Playing the “switch the latest installed scripts off and on to see what’s having hiccups” revealed that the Dashboard Level Progress Indicator is trying to run on the community forums as well and that’s what causes the message prompt.
Is it intended to do that? Is it just me who’s having that happen?
What can I do to avoid the unwanted redirect to the Open Framework thread?
For now I’ll just have to toggle the script on and off during durtling on the forums… maybe it’s a sign from the Crabigator that I’m shirking my duties.
I would like to show that I too would like for some way to still see the progress of each individual kanji like @steelviper77 mentioned. Maybe have a hover-over option that displays a list of kanji with their srs indicator like how it is in vanilla.
Is there a particular reason the current script does render - retrieve and then does not render again?
When coming back from a review session, the old script used to render the cached status (pre-review), then retrieved the updates and rendered again - a visual indication of what you accomplished during the review.
Currently, I need to refresh the page to get the updates. Same after lessons - the display is always of the previous state.
I love the updates you’ve done so far (barring the mentioned one ). I can now choose to keep the bars visible until all of the items are guru’ed at least once!
The problem here is that I have no more levels that satisfy
l.data.passed_at == null
after hitting 90% kanji passed on level 60. Assuming level 60 if the level cannot be found makes the script work again.
PS: I added a link to this thread to the Overview of scripts as a replacement for the original Dashboard Level Progress Detail so people don’t keep getting linked to the script that no longer works out of the box
Works perfectly! I’m well aware of how difficult it is to debug situations you can’t reproduce locally - I’ve heavily relied on others loading my scripts too…