Is your feature request related to a problem? Please describe.
Recently, I was doing some index cleanup on a production database. I found your tool to be very helpful! Thank you.

However, I realized that we also had a few weird things with some of the indexed views that had been created.

None of the clustered indexes on the views were created with data compression. Additionally, some of the non clustered indexes on the views were redundant and/or not very useful.

Describe the solution you'd like
It would be nice if sp_IndexCleanup also included indexes on views in its results. However, I am not certain how you want to handle a view name as an input parameter. Do you want to use @table_name and just assume it could also be a view? Or do you want to change it to @object_name or some other such thing? Or add an additional parameter for @view_name?

Describe alternatives you've considered
sp_BlitzIndex has some support for views, but it's not very robust. That one has an @objectname parameter, which can get you some information on the indexes for a view.

Are you ready to build the code for the feature?
It's possible I can work on this one, but not for a few weeks as I am traveling. If you want me to work on it, just let me know what you are thinking regarding parameters and such.

IMPORTANT: If you're going to contribute code, please read the contributing guide first.
https://github.com/erikdarlingdata/DarlingData/blob/main/CONTRIBUTING.md