Skip to content
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

Add a contest clock to WTI #1027

Open
clevengr opened this issue Dec 14, 2024 · 0 comments · May be fixed by #1034
Open

Add a contest clock to WTI #1027

clevengr opened this issue Dec 14, 2024 · 0 comments · May be fixed by #1034
Assignees
Labels
enhancement New feature or request NEXT Contest Consider fixing for next contet Usability Issue This is an enhancement for which there is currently no usable workaround

Comments

@clevengr
Copy link
Contributor

Feature Description:
The WTI screen should display a "contest clock" at all times. It might be useful to have both "Elapsed:" and "Remaining:" displays.

Do you have any specific suggestions for how your feature would be implemented in PC^2?
It's probably going to involve changes to the app-header component in the shared module under the WTI src folder.

Additional context: please provide any additional information that will help us in considering your feature request.

Angular already defines a library containing a countdown widget; this should probably be used. See https://blog.devgenius.io/how-to-show-a-countdown-timer-in-angular-using-ngx-countdown-9835c98de101 for details.

@clevengr clevengr added enhancement New feature or request Usability Issue This is an enhancement for which there is currently no usable workaround NEXT Contest Consider fixing for next contet labels Dec 14, 2024
@clevengr clevengr self-assigned this Dec 14, 2024
clevengr pushed a commit to clevengr/pc2v9 that referenced this issue Jan 5, 2025
This commit removes the requirement that the contest be running in order
for the WTI-API /clarifications endpoint to return clars; now the only
requirement for returning clars is that the client "is-logged-in".

The commit also changes the requirement in the /problems endpoint:
previously the contest had to be RUNNING in order to see problems; now,
it just has to have been STARTED (i.e., there must have been greater
than zero "elapsed time".  This allows teams to see problems during a
pause.

Note that this commit is part of a PR for
pc2ccs#1027, but it solves
pc2ccs#1029 as well.
clevengr pushed a commit to clevengr/pc2v9 that referenced this issue Jan 11, 2025
This commit removes the requirement that the contest be running in order
for the WTI-API /clarifications endpoint to return clars; now the only
requirement for returning clars is that the client "is-logged-in".

The commit also changes the requirement in the /problems endpoint:
previously the contest had to be RUNNING in order to see problems; now,
it just has to have been STARTED (i.e., there must have been greater
than zero "elapsed time".  This allows teams to see problems during a
pause.

Note that this commit is part of a PR for
pc2ccs#1027, but it solves
pc2ccs#1029 as well.
@clevengr clevengr linked a pull request Jan 12, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request NEXT Contest Consider fixing for next contet Usability Issue This is an enhancement for which there is currently no usable workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant