Show Best and Mean columns for 3x3x3 Blindfolded results

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
react, typescript
Domain
frontend

Research direction

Start at the competition results page's summary-column selection for 3x3x3 Blindfolded and trace how the best-of-3 format maps columns to result fields and record tags. Add regression coverage for this round format, then verify the table shows Best from result.best and Mean from result.average while other event and round-format behavior stays unchanged.

Written by the indexing model from the issue text.

Description

Problem

On the competition results page for a 3x3x3 Blindfolded round, both summary columns are labeled Best and both render the single result. This is visible on Rubik's WCA European Championship 2026, 3x3x3 Blindfolded Round 1.

The round uses a best-of-3 format, so the current format-only column selection treats both summary columns as single even though WCIF/WCA Live also provides the mean in average.

Expected behavior

The summary columns should be shown in this order:

  1. Best, using result.best and the single record tag
  2. Mean, using result.average and the average record tag

Acceptance criteria

  • 3x3x3 Blindfolded result tables render Best and Mean, not two Best columns.
  • The two columns display the corresponding best and mean values.
  • Record badges remain attached to the correct result type.
  • Other event and round-format column behavior remains unchanged.
  • Add regression coverage for a 3x3x3 Blindfolded best-of-3 round.
Dominant language
TypeScript
Stars
11
Forks
12
Avg merge
34m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder13/Competitor-groups

All issues in coder13/Competitor-groups

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.