feat: Add prefer_sliver_prefix rule

[naipaka]

🔗 Related Issues

• None

🙌 What's Done

• Add prefer_sliver_prefix rule

✍️ What's Not Done

• None

🖼️ Image Differences

🤼 Desired Review Method

• Correction Commit
• Pair programming

Note

It is possible that a reviewer's will may cause a method to be implemented that is not selected.

📝 Additional Notes

This rule ensures that class names are consistent and easily recognizable as returning a Sliver widget!

Pre-launch Checklist

• I have reviewed my own code.
• I have added tests that prove my fix is effective or that my feature works.
• I updated/added relevant documentation (doc comments with ///).

[riscait]

This is another great rule!

Would a rule like "prefer_to_include_sliver_in_name" be better so that it is not limited to Prefix?
example: MyWidget.sliver() , MyExcellentViewWithSliver() , AltiveSliverWidget() .

[naipaka]

@riscait

Would a rule like "prefer_to_include_sliver_in_name" be better so that it is not limited to Prefix?
example: MyWidget.sliver() , MyExcellentViewWithSliver() , AltiveSliverWidget() .

Indeed, having some flexibility might be beneficial✍️

Including the constructor could result in significant changes, so how about creating a separate improvement issue and having someone else handle it? 💭

[riscait]

Including the constructor could result in significant changes, so how about creating a separate improvement issue and having someone else handle it? 💭

Let's do that!

[naipaka]

I created the following issue!
#36