-
Notifications
You must be signed in to change notification settings - Fork 24
[tools] Separate changing to contest directory and getting problems list #166
New issue
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
base: master
Are you sure you want to change the base?
[tools] Separate changing to contest directory and getting problems list #166
Conversation
That's fine - duplicating some code for tests is OK with me.
Right. Do you want to spend some more time on this for this PR? (I assume that's why it's draft for now.) I'm not exactly sure myself yet how we should handle this. One possibility:
|
All right 🙂
Correct 😋
Sounds good, but I don't like the fact that the arguments need to be parsed twice. I was thinking of something like the following (but I'll need to try this to see how it works out):
Maybe 2.i should be checked before 1.iv, but that requires a bit more rewriting. I'll experiment with it for a bit 🙂 |
@mpsijm what's the status here? I kinda forgot what this was about |
If I remember correctly, this is mostly to make the parsing of the personal config file more consistent. It's mostly a code cleanup that doesn't really have high priority, but I would still like to finish it if I do have the time 😛 |
Related to RagnarGrootKoerkamp#166: this bug existed because new_problem did not change directory to args.contest.
Related to RagnarGrootKoerkamp#166: this bug existed because new_problem did not change directory to args.contest.
Related to RagnarGrootKoerkamp#166: this bug existed because new_problem did not change directory to args.contest.
Related to RagnarGrootKoerkamp#166: this bug existed because new_problem did not change directory to args.contest.
Copying part of the discussion from #163 (comment):
@RagnarGrootKoerkamp:
@mpsijm: