Hi @nejckikelj, and thanks for your PR.

Before looking closely into your code changes, it would be great if you could add some unit tests for these new parameters. A new example in the docs would be appreciated as well.

Hi @just-the-benno, thanks for the comment. Unit tests and docs example added.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.49%. Comparing base (28bc599) to head (a89e42c).
Report is 206 commits behind head on dev.

@@            Coverage Diff             @@
##              dev    #5463      +/-   ##
==========================================
+ Coverage   89.82%   90.49%   +0.66%     
==========================================
  Files         412      396      -16     
  Lines       11878    12140     +262     
  Branches     2364     2369       +5     
==========================================
+ Hits        10670    10986     +316     
+ Misses        681      621      -60     
- Partials      527      533       +6     

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

Just checking on this PR ? :)

Hello,

Thank you for the PR. My apologies for the delay in response.

I need to consult with a team member to decide whether we should close this PR or revive it and merge.

@henon, do you think I should revive this PR by resolving conflicts? This PR makes sense. Ideally, having a RenderFragment would provide more flexibility, but with rating, it's a bit more complex as it requires context data such as read-only, hover states, selection, and potentially more which sounds more like a component rework and cba to do that. So either this or nothing.

Yes, this makes sense.

Sorry, misclicked ;)

@henon this is ready for review.
Fixed the tests to use FluentAssertion & nits and little fix for the SelectIconColor to get SelectedValue from the GetState.