[Docs] Fix the controlled RadioGroup example

[sookmax]

Closes #6056

Hey guys I have one question.

Would it be better to just add the empty string ('') check over here?

react-spectrum/packages/@react-aria/radio/src/useRadio.ts

Lines 82 to 92 in 9390151

	let tabIndex: number | undefined = -1;
	if (state.selectedValue != null) {
	if (state.selectedValue === value) {
	tabIndex = 0;
	}
	} else if (state.lastFocusedValue === value || state.lastFocusedValue == null) {
	tabIndex = 0;
	}
	if (isDisabled) {
	tabIndex = undefined;
	}

to something like this?

let tabIndex: number | undefined = -1;
- if (state.selectedValue != null) {
+ if (state.selectedValue != null && state.selectedValue !== '') {
  if (state.selectedValue === value) {
    tabIndex = 0;
  }
} else if (state.lastFocusedValue === value || state.lastFocusedValue == null) {
  tabIndex = 0;
}
if (isDisabled) {
  tabIndex = undefined;
}

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

Docs

http://localhost:1234/react-aria/useRadioGroup.html#controlled-value

radio_controlled_keyboard.mov

🧢 Your Project:

[snowystinger]

GET_BUILD

[snowystinger]

Thanks @sookmax this is the correct fix, we allow falsy id's such as empty strings. So you could do something like this https://stackblitz.com/edit/vitejs-vite-28q1zf?file=src%2FApp.tsx,package.json

[rspbot]

Build successful! 🎉

• View the storybook
• View the storybook-17
• View the storybook-16
• View the documentation

[rspbot]

## API Changes

unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any', access: 'private' }
unknown top level export { type: 'any', access: 'private' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'identifier', name: 'Column' }
unknown top level export { type: 'identifier', name: 'Column' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }
unknown top level export { type: 'any' }

[sookmax]

@snowystinger Ah that's interesting! Never imagined there would be a case where a radio value actually is "" haha. Thanks for sharing the sandbox!