fix(radio-button): Prevent invalid/warn states when disabled/readonly

[anuanto966]

Fixed RadioButton components in both React and Web Components to not show invalid/warn states when in disabled or readonly state, as users cannot interact with these components in those states.

Closes #20730

Changelog

Changed

• Instead of using readOnly state to check if should display warnings or not, Radio Button now also checks if component is disabled. This way, warnings will not be shown if the component is disabled/readOnly.

Testing / Reviewing

• Access Radio button on storybook (/?path=/story/components-radio-button--default) and change the state to "Invalid = true" and "disabled = true". The invalid message should not be shown.
• Repeat above test with "readOnly = true" instead of disabled. The invalid message should not be shown.
• Repeat the two tests above using "warn = true" instead of "invalid = true". The warning message on both scenarios should not be shown.

PR Checklist

As the author of this PR, before marking ready for review, confirm you:

• Reviewed every line of the diff
• Updated documentation and storybook examples
• Wrote passing tests that cover this change
• Addressed any impact on accessibility (a11y)
• Tested for cross-browser consistency
• Validated that this code is ready for review and status checks should pass

More details can be found in the pull request guide

[netlify]

✅ Deploy Preview for v11-carbon-web-components ready!

Name	Link
🔨 Latest commit	20455f8
🔍 Latest deploy log	https://app.netlify.com/projects/v11-carbon-web-components/deploys/690d6a203fe89a0007d36630
😎 Deploy Preview	https://deploy-preview-20810--v11-carbon-web-components.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for carbon-elements ready!

Name	Link
🔨 Latest commit	20455f8
🔍 Latest deploy log	https://app.netlify.com/projects/carbon-elements/deploys/690d6a208ac01f000804a598
😎 Deploy Preview	https://deploy-preview-20810--carbon-elements.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for v11-carbon-react ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	20455f8
🔍 Latest deploy log	https://app.netlify.com/projects/v11-carbon-react/deploys/690d6a2017fcc80008e822c3
😎 Deploy Preview	https://deploy-preview-20810--v11-carbon-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codecov]

Codecov Report

❌ Patch coverage is 98.63014% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 92.42%. Comparing base (9201e68) to head (20455f8).
⚠️ Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
...onents/src/components/radio-button/radio-button.ts	98.36%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #20810      +/-   ##
==========================================
+ Coverage   92.41%   92.42%   +0.01%     
==========================================
  Files         515      515              
  Lines       37524    37591      +67     
  Branches     5693     5735      +42     
==========================================
+ Hits        34676    34745      +69     
+ Misses       2700     2697       -3     
- Partials      148      149       +1     

Flag	Coverage Δ
main-packages	85.55% <100.00%> (+0.01%)	⬆️
web-components	96.73% <98.48%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[riddhybansal]

Hi This Looks God to me!! Thanks for your contribution 💯

[riddhybansal]

Hey this looks good

Small Suggestions for Improvement
Code Consistency

Consider using useNormalizedInputProps in all components rather than creating separate validation logic:

normalizedProps = useNormalizedInputProps({
id, disabled, readOnly, invalid, invalidText, warn, warnText,
});

Then reference normalizedProps.invalid and normalizedProps.warn for validation states
Our input controls already use this pattern, which makes future fixes simpler (just update the hook once).

Here is the reference #20808

[anuanto966]

Then reference normalizedProps.invalid and normalizedProps.warn for validation states Our input controls already use this pattern, which makes future fixes simpler (just update the hook once).

Here is the reference #20808

Hi @riddhybansal these changes are done. Could you please review . Also can you please add the label hacktoberfest to this PR.

[riddhybansal]

Please run "yarn test -u" in root for test cases to pass.

[anuanto966]

yarn test -u

@riddhybansal Ran the tests in local and passed