Skip to content

[Bug Fix] Fix number of dots per segment#432

Open
shraddha-bajare wants to merge 1 commit into
mainfrom
issue_403
Open

[Bug Fix] Fix number of dots per segment#432
shraddha-bajare wants to merge 1 commit into
mainfrom
issue_403

Conversation

@shraddha-bajare

@shraddha-bajare shraddha-bajare commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

Fixes #403

Root Cause:

The bug is a mismatch between what Radar.jsx renders and what the About page documents.
e.g
resqui has all three tiers (rs:AnalysisCode, rs:PrototypeTool, rs:ResearchInfrastructureSoftware) and functional_suitability as a dimension — so the radar renders 3 dots (one per tier). But when the segment is clicked, Home.jsx's filteredTools correctly returns only 1 tool (since resqui is a single entry).
So the dot count and the list count are structurally inconsistent.
As per decision About page says:If a tool applies to multiple tiers, it is placed in the lowest applicable tier.
but the code places it in all applicable tiers.

Fix applied:
In Radar.jsx, replace the multi-tier push with a single minimum tier. This makes the dot count equal to the tool count per segment, so clicking "Functional Stability" shows 1 tool and 1 dot — consistent with the About page

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.

Rose diagram: confusion about number of dots per segment

1 participant