chore: rename Button 'styles' prop to 'style' for consistency#590
chore: rename Button 'styles' prop to 'style' for consistency#590SupertigerDev merged 1 commit intoNerimity:mainfrom
Conversation
Button was the only component that used 'styles' instead of 'style'; it also silently ignored the normal 'style' property inherited from <button>, which caused at least one bug -- the explore themes button in interface settings was styled, but those styles were ignored.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (16)
📝 WalkthroughWalkthroughA systematic refactoring renames the Button component's inline styling prop from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Button was the only component that used
stylesinstead ofstyle; it also silently ignored the normalstyleproperty inherited from<button>, which caused at least one bug -- the explore themes button in interface settings was styled, but those styles were ignored.This is literally just using a LSP rename from
stylestostyle, renaming"styles"to"style"in thesplitPropslist, and adding"style"to theOmitsection ofButtonProps. There are no remaining uses ofstyles=in the codebase, so I believe it got everything.Screenshots
The current preset theme list in interface settings; only the button is clickable in the explore pane.

With this PR; there are no new styles, just that the existing styles are correctly applied. The entire pane is clickable.

Did you test your code?
Tested on Firefox on Linux and Chrome on Android.
Checklist
Text/content changes support internationalization (i18n)(N/A)Any new user-facing strings are properly localized(N/A)Summary by CodeRabbit