Repository navigation
Changes since 3.4.0, in #281 – #288.
Features
- JUNGOL. Turn on "Use JUNGOL" under Problem sites in the popup, and allow the access Chrome asks for. (#286)
- When you submit on a problem page and the judge accepts it, a panel at the bottom left shows the GitHub and Notion buttons. The upload has the problem ID, title, tier and tags, such as
JUNGOL/1000 - 두 정수 더하기 (A+B).cppon GitHub. - With auto upload on, the accepted submission is uploaded once without a click. (#287)
- The extension only watches the judge request that the page sends, and reads a copy of its answer. It never calls the JUNGOL API and does not upload the problem statement.
- When you submit on a problem page and the judge accepts it, a panel at the bottom left shows the GitHub and Notion buttons. The upload has the problem ID, title, tier and tags, such as
- New store screenshots with the popup, the three sites and the results. (#288)
Fixes
- Programmers: clearing the editor no longer uploads the starting code. (#284)
- Codeforces: the problem name in the upload comes from the problem link, not its ID. (#285)
Development
- Programmers uses the same in-page buttons and messages as the other sites. (#284)
- Codeforces and JUNGOL tests use pages and data cut from the real sites. (#285, #286)
- CI runs on Node 22 and 24, and Prettier checks the Markdown docs. (#282, #283)
CLAUDE.mdlists every place to update when adding a judge site. (#281)- 464 tests.
Upgrading
- Chrome Web Store: the update arrives by itself, with no new permission warning. Turn JUNGOL on in the popup if you use it.
- Unpacked: pull or download this version and click Reload on the extension card in
chrome://extensions/. Nothing else is needed.