In order to make parsing the config easier and less prone to breakage and security problems, let's switch it to JSON. If we set it up at a page that ends in ".js", that will also enable syntax highlighting.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Cyberpower678 | T120433 Migrate dead external links to archives | |||
| Resolved | Cyberpower678 | T140377 Build robust testing framework for InternetArchiveBot (epic) | |||
| Resolved | Cyberpower678 | T141347 Create and test v1.2 of InternetArchiveBot (tracking) | |||
| Resolved | Cyberpower678 | T141802 Convert InternetArchiveBot config system from wikitext to JSON |
Event Timeline
Comment Actions
I see one problem to this, the ideal location of the config page is when it's located in the userspace of the bot. JS pages are locked to outsiders except for admins. :/ To work around this, I would either login as the bot to edit the config page, or put the JS page in my userspace. It's nothing major, just seems like a minor annoyance to me. :p