We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey, I just tried out this tool. It seems to get the job done, but I feel the UX could be a bit better.
Improved installation process
pip
Currently username / password has to be specified inside utils/conig.py
utils/conig.py
$HOME/codeforces
Bundled under one main script
idne
parse
submit
Improvements to the parse script
Add support for Python language
Take optional argument for problem name: A, B etc.
A
B
In general, the test.sh can be refactored
test.sh
idne run
We could even fetch the problem statement (the entire text) and add it to the problem code file itself (.cpp, .py)
.cpp
.py
So one can look at the problem statement in the editor itself
Similarly, the test cases could be written inside the code file too
Then, the idne run command could just extract the test cases from the code file itself, and run them!
What are your thoughts?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hey, I just tried out this tool. It seems to get the job done, but I feel the UX could be a bit better.
Improved installation process
pip
Currently username / password has to be specified inside
utils/conig.py
$HOME/codeforces
Bundled under one main script
idne
that has two argumentsparse
submit
Improvements to the
parse
scriptAdd support for Python language
Take optional argument for problem name:
A
,B
etc.In general, the
test.sh
can be refactoredidne run
We could even fetch the problem statement (the entire text) and add it to the problem code file itself (
.cpp
,.py
)So one can look at the problem statement in the editor itself
Similarly, the test cases could be written inside the code file too
Then, the
idne run
command could just extract the test cases from the code file itself, and run them!What are your thoughts?
The text was updated successfully, but these errors were encountered: