In #549, we added unittests for dispatch AtCoder and Codeforces.
To increasing test coverage, we should add unittests for other contest (HackerRank, CS Academy, ...).

Not only tests for all other contests, tests for the part of contests are welcome.

It would be great to add a subset of the now only jury available stats also to the team and public pages.

I'm thinking of the submission graph over time (but all rejected verdicts bundled into one, of course nothing after the freeze) and the total number of attempts/corrects.

There are two sets of refactoring that can be performed on our codebase to make them more efficient and utilize the full potential offered by Qt Framework. See below:

1. There is no need to explicitly call delete on widgets that are allocated on Heap as long as in their constructor we have specified the parent widget for it. Consider this example below:

class Widget: public QObject

The reasoning for this is the same as for problem testers; problem testers can be used as a model for this feature.

Description

該当ページ:

• https://online-judge-tools.github.io/verification-helper/
• https://online-judge-tools.github.io/verification-helper/setup.py
• https://online-judge-tools.github.io/verification-helper/onlinejudge_verify_resources/_layouts/__init__.py など

.verify-helper/docs/_config.yml での exclude の指定漏れ

Other notes

• Will you try to create a pull request?
  • no

I think Monaco would work quite well; they have reasonable markdown/mdx support.

https://microsoft.github.io/monaco-editor/