Arctos6135 / Arctos6135/scouting-database

Better define specific scouting output's behaviour in Strategy.js

Open
#30 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Both NMA and ScoutingOutput have a toggle for whether they refer to data from all events or the current one. They use the same piece of Strategy.js' state for this, and should always do the same thing, but the checkboxes which control specific_scouting_output's value can appear different to the user. It's possible that they also become unaligned with their labelling.
Confirm that this isn't happening, and make them consistent to each other and what a user would expect. Possibly move this checkbox to the header.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading Strategy.js and tracing the state used by the NMA and ScoutingOutput controls for specific_scouting_output. Compare their checkbox visibility and labels, then verify that both controls consistently represent the all-events versus current-event choice and match user expectations.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.