Skip to content

Debug the dropdown menu of superseding score set shows private score sets problem. - #709

Merged
EstelleDa merged 2 commits into
release-2026.2.4.1from
buxfix/estelle/708/supersedeScoreSetDropDownMenu
Aug 11, 2026
Merged

Debug the dropdown menu of superseding score set shows private score sets problem.#709
EstelleDa merged 2 commits into
release-2026.2.4.1from
buxfix/estelle/708/supersedeScoreSetDropDownMenu

Conversation

@EstelleDa

Copy link
Copy Markdown
Member

No description provided.

const licenseSearch = useAutocomplete<License>('/licenses/active')

const extractScoreSets = (data: unknown) => ((data as Record<string, unknown>)?.scoreSets as ShortScoreSet[]) || []
const extractScoreSets = (data: unknown): ShortScoreSet[] => {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Perfect, looks good. supersededSearch and metaAnalyzesSearch both want public score sets only. My only suggestion is that we rename extractScoreSets to something that makes it clear that we are keeping only public score sets now.

@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 6.656%. remained the same — buxfix/estelle/708/supersedeScoreSetDropDownMenu into release-2026.2.4.1

@EstelleDa
EstelleDa merged commit fde9801 into release-2026.2.4.1 Aug 11, 2026
1 check passed
@EstelleDa
EstelleDa deleted the buxfix/estelle/708/supersedeScoreSetDropDownMenu branch August 11, 2026 02:26
@bencap bencap mentioned this pull request Aug 12, 2026
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.

The dropdown menu of superseding score set has private score sets in creating a new score set

3 participants