[Userscript] Burn Progress

WaniKani API And Third-Party Apps
42

Version 1.5 pushed to greasyfork. Let me know if there are any further prbolems. (Edit: where nothing can go worng.)

Since the WK update, the /dashboard path is no longer guaranteed to be present.

I’m using this matcher:

// @match        https://*.wanikani.com/*

Which should match any of the following:

https://wanikani.com
https://www.wanikani.com
https://preview.wanikani.com
https://foo.wanikani.com
https://wanikani.com/dashboard
https://www.wanikani.com/dashboard
https://preview.wanikani.com/dashboard
https://foo.wanikani.com/bar
43

Won’t this also match the community forum?
That doesn’t have WKOF running which was giving me warning popups earlier.

2 Likes
44

Hmm…

I’m not getting that popup for some reason, but yes. Was trying to future-proof a bit, but it looks like explicit matches may be best:

// @match        http*://wanikani.com
// @match        http*://www.wanikani.com
// @match        http*://preview.wanikani.com
// @match        http*://wanikani.com/dashboard
// @match        http*://www.wanikani.com/dashboard
// @match        http*://preview.wanikani.com/dashboard

Both / and /dashboard go to the dashboard, but there appear to be links to both in various places.

Version 1.6 coming up has been pushed to greasyfork. Now to update my other dashboard scripts.

45

There’s a problem I just came across using the Violentmonkey user script addon on Firefox. I’m not sure whether or not it appears with other addons and/or browsers as well.

It looks like you need to explicitly provide a path in the @match rules, even if the rule should match a whole domain. So you need to go from

// @match http*://wanikani.com
// @match http*://www.wanikani.com
// @match http*://preview.wanikani.com

to

// @match http*://wanikani.com/
// @match http*://www.wanikani.com/
// @match http*://preview.wanikani.com/

Note the slash at the end of each line. The other @match rules have /dashboard as the path and seem to be fine.

1 Like
46

Thanks for the heads up. I’ll take a look when I have a moment. I’ve not done reviews in forever and don’t use Firefox nor ViolentMonkey, but this looks like an innocuous change (famous last words).

47

This script is a great motivator. Thank you!

1 Like
48

The latest changes in the dashboard’s HTML structure necessitate a new modification. The class name that the script used to determine where to insert the bar isn’t used anymore. The best solution would probably be to insert the bar on top of .dashboard__content (two underscores) instead of the outdated .progress-and-forecast.

2 Likes
49

Apologies, I’ve not been maintaining any of my scripts. Will try to get to this over the next few days.

2 Likes
50

Fixed. Sorry for the absurdly slow response!

Fixed. Thanks for the prompt.

The script was updated on greasyfork as well as on GitHub

Let me know if there are any further issues

1 Like