data from the website called Modarchive, the
functions provided inside the
scraper::requests module send requests to
modarchive, parse the webpage and provide you with the requested info.
Do check out the docs for each module if you need more info about their
usage, in the
scraper::resolver module you can find function(s) which
search modarchive for the provided info. Again, docs are your friend.
Check out the examples/ directory on the github repo for all examples using the library
This feature basically enables you to make the library retry infinitely regardless of errors until Modarchive gives in
Overriding the default values
This library functions by using stable "anchor" points to start from and extract meta-data which are hardcoded in the source but since it's better to future proof in case of an event like a small design change in Modarchive there is a way to override the main anchor points without needing to update the whole program, and that is an extremely simple config file which is enabled by the "overridable" feature and is located depending on the platform, using the crate platform-dirs to determine the config file folder which your program should modify in order to change anchor values, on linux for example its located at:
in header-less csv and is read as "module_filename_line, module_info_line, module_download_line (the download count)" if you're still unsure of what they are view the source page on an unnominated module of modarchive and check out the lines which are hardcoded in the source-code, for the nominated modules these are all raised by 6 since the nomination badge adds 6 lines to the source page, which also has an anchor but since there haven't been any problems even after the small shift which added the scenesat mirror banner i haven't included them in the overrides but its very easy to do so if need be