Linked to the previous one (#1): currently, each update load the whole lot of solutions, while in most cases only a few bunch of those would need to be. That would be good (for cw's servers too) that a limitation can be put on this.
problem:
require to find how to be sure to identify what's needed to be downloaded or not.
archiving the last completed kata won't be enough. Leads to a wrong update in the following case:
last update of solutions done, archiving the kata at the top of the list as "limiter"
new katas done by the user (let's say 10 new ones)
the user complete the "limiter" in a new language
new update of the script => it will miss the 10 new ones
'just thought that maybe you could just store the date of the last update and download the pages until you reach a date that is older than the last update? Surely better, yes x)
Linked to the previous one (#1): currently, each update load the whole lot of solutions, while in most cases only a few bunch of those would need to be. That would be good (for cw's servers too) that a limitation can be put on this.
problem:
require to find how to be sure to identify what's needed to be downloaded or not.
archiving the last completed kata won't be enough. Leads to a wrong update in the following case:
'just thought that maybe you could just store the date of the last update and download the pages until you reach a date that is older than the last update? Surely better, yes x)
cheers!