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

Added contestant number (order) for WSContest contest page #70

Closed
wants to merge 1 commit into from

Conversation

Avartii
Copy link
Contributor

@Avartii Avartii commented Jul 10, 2024

I have added contestant number (order) for WSContest contest page. It will be beneficial to the contestant as well as admins to be able to tell, for example: who are the top 10 contestant, how many total contestants are there, etc.

@Avartii
Copy link
Contributor Author

Avartii commented Jul 10, 2024

Hello, @samwilson will you please review this commit and provide me feedback for the same.

Copy link
Member

@samwilson samwilson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this! Just one small thing to fix, then it looks like it's ready to go.

Did you have any troubles getting this set up to work on and test locally?

@@ -55,6 +55,7 @@
<caption style="caption-side: top">{{ msg('scores-legend', [score_calculation_interval~'']) }}</caption>
<thead>
<tr>
<th>{{ msg('rank') }}</th>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The rank message needs to be added to i18n/en.json and i18n/qqq.json.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay I got your point, submitting the updated patch very soon! Thanks for your guidance.

@Avartii
Copy link
Contributor Author

Avartii commented Jul 11, 2024

Thanks for this! Just one small thing to fix, then it looks like it's ready to go.

Did you have any troubles getting this set up to work on and test locally?

No, I'm not having any issues when testing locally; I just assumed it was a minor edit and so didn't checked it thoroughly.

@samwilson
Copy link
Member

No, I'm not having any issues when testing locally; I just assumed it was a minor edit and so didn't checked it thoroughly.

Okay, no worries.

It looks like you've created #73 as a replacement for this PR, is that right? Let's close this one and continue the discussion over there. (In general, you don't need to create separate PRs for fixing review issues, you can just push more commits to the branch here.)

@samwilson samwilson closed this Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants