Distinguish Activity Rows from Unique Participants with React (2027)

A report claims three people when one person appears twice. This React debugging guide starts with that visible symptom and reduces it to a small, reproducible contract. The goal is to explain why the result is wrong, make one focused correction and preserve the corrected behaviour in a regression check.

Use the exercise for 2027 study or portfolio practice. All records and situations are fictional. Start with basic React knowledge and a local learning environment. Keep the example small until the original failure, accepted policy and expected output can be explained without opening the implementation.

Recognize the failure

The metric counts attendance actions but its label describes unique individuals. The underlying arithmetic is correct for a different question.

Write the symptom down before changing the code or configuration. Separate what was observed from what you suspect. Record the exact input and the operation that produced the result; a statement such as “the totals look odd” is harder to investigate than a fixture whose accepted outcome is explicit.

Agree on the contract

Expose row count and distinct fictional participant count as separately named metrics. Use a stable participant identifier for distinctness.

The policy in this exercise is deliberately scoped. A matching implementation must produce the expected structure and types, preserve the supplied fixture, and communicate a defined rejection as a completed outcome. Treat null, zero, empty collections and error objects according to this case rather than merging them into one generic fallback.

Reproduce it with this input

[
  "person-1",
  "person-1",
  "person-2"
]

Expected outcome:

{
  "attendance_actions": 3,
  "distinct_people": 2
}

Compare the complete result, including value types and any error category. A correct-looking label is insufficient if the transport value or stored state has a different meaning. Keep this golden fixture unchanged while exploring additional examples so the original failure remains reproducible.

Read the checked reference

The collection includes a complete Python reference and executable checks. Save the text download as reference_checks.py to run it locally. The following function is an excerpt from that file; imports and any helpers such as number, instant or ContractError are defined there. The check runner turns a deliberate contract rejection into the error object shown above.

def rows_versus_distinct_people(values):
    return {'attendance_actions':len(values),'distinct_people':len(set(values))}

The Python reference is the behavioural oracle for the small fixture. For this React article, implement the equivalent behaviour at the interface-to-domain boundary. The reference check is not evidence that a separate framework, device, database or distributed system has already been implemented or tested.

Apply the fix in React

Place the rule behind a small transformation or validation function. Keep displayed values separate from the underlying typed result. Show the actual input state, the accepted output and an understandable recovery path. Preserve a distinction between a loading screen, an empty result and a rejected operation.

Keep the fixture separate from component state and derive the displayed result from the current filter. Avoid storing the same total in a second state variable when it can be calculated from the records. Use stable record identifiers as list keys, and make loading, empty and error states visible rather than hiding them behind a spinner.

Connect these React design concerns to the case while reviewing the implementation:

• Single source of truth for state.
• Controlled filter inputs.
• Stable component keys.

Start with the smallest operation that can return the expected outcome. Add the surrounding interface, request adapter, query or verification job only after that operation is understandable. Observe the input immediately before the boundary and the output immediately after it; this helps identify a conversion or state change introduced by the adapter itself.

Add the regression and a valid control

Use person-one twice and person-two once. Require three attendance actions and two distinct people.

Replay the fixture through the calculation and then through the screen. Assert the user-visible outcome after the action settles. Include a reset or second interaction to reveal stale derived state and avoid treating a screenshot alone as a complete regression check.

Preserve these track-specific checks as well:

• Changing a filter must update the result.
• A rerender must not reset unrelated input.
• An empty match needs an explanatory message.

Run the complete reference set from the repository root with python reference_checks.py. Save the actual output with the source revision. When adapting the case, keep the expected result independent of the implementation under test; generating an expected value with the same faulty function would reproduce the defect inside the test.

Explain where this example stops

Display names are unreliable identity keys. Real participant information is unnecessary for this exercise; keep the fixture fictional and avoid cross-system identity assumptions.

Document one consequence of the chosen policy and one reasonable alternative. If the product contract changes later, update the explanation and expected result deliberately, then add a case that distinguishes the new meaning from the old one. A passing local fixture should stay attached to its stated assumptions.

Present the investigation in a portfolio

Show the failing observation, the input, the policy decision and the corrected result in that order. Include the focused diff, a valid control, the regression evidence and a short explanation of the boundary you changed. Give another learner the fixture and setup instructions so they can repeat the investigation rather than relying only on a screenshot.

For a useful extension, vary one part of the fixture while keeping the policy fixed. Explain the predicted outcome before running it. If the prediction and observation disagree, record that disagreement as the next investigation instead of silently changing the expected value to match the implementation.

Questions learners ask

Does the sample define the only correct product policy?

It defines this lab's policy. Use the stated boundary notes to compare alternatives, then choose the behaviour your own feature promises. Different policies need distinguishable tests and clear labels.

What has actually been executed?

The shared Python reference runner checks this fixture, its expected output and input preservation. A React adaptation remains a practical exercise until its own implementation and evidence are added. The collection's verification report records the scope of the checks.

How should I use this while choosing a course?

Use the failure and regression as a concrete discussion point. Explore the related Groot Academy course and ask about its current syllabus, learning mode and hands-on exercises. Confirm batch availability directly with the academy.

Consult the official React documentation for the tools you use, and the Python reference documentation for this case for the illustrated parsing, representation or library behaviour. The 2027 label identifies a study edition rather than a prediction about future releases or hiring.

Continue with Use Weights in a Weighted Average with React, or explore Distinguish Activity Rows from Unique Participants with Angular. These companion practice guides are part of the 2027 learning collection.