Windowscommunitytoolkit: Proposal: Rename MasterDetailsView control to ListDetailsView

[mrlacey]

In line with efforts elsewhere to reflect more inclusive language (example), is now a good time to change the name of the MasterDetail control?

I suggest ListDetail, ListAndDetail, ListWithDetail, ListAndContent, or ListWithContent as alternatives. Suggestions welcome.

[msftbot[bot]]

Hello mrlacey, thank you for your interest in Windows Community Toolkit!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible.. Other community members may also answer the question and provide feedback 🙌

[RosarioPulella]

@mrlacey Thanks for raising this issue! We have an effort to rename out the master branch to main in https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/3062 but we must have overlooked this.

[RosarioPulella]

Personally, I am leaning towards ListDetail. I feel like is just as concise as MasterDetail but more descriptive.

[Kyaa-dost]

@mrlacey Thanks for highlighting the issue and providing suggestions!!

@michael-hawker @azchohfi thoughts on this?

[michael-hawker]

Thanks @mrlacey - I thought we had an issue for this already somewhere, but guess not, thanks for filing!

We have had this on our radar though. We were waiting for official guidance on the recommended naming for this control from the design group within Microsoft. Seems like Xamarin has moved forward, so let me revive that thread as I hadn't heard back yet.

This is definitely something we should resolve for 7.0.

@RosarioPulella for the master to main branch, we've been waiting for the official GitHub tools which will help with the redirects as otherwise we'll break a bunch of folks who've cloned the repo.

[michael-hawker]

Followed-up, seems like consensus hasn't been reached yet but some folks have continued forward, which we probably will need to do before 7.0 ships...

I think ListDetailsView is probably the best choice for now to move forward.

Eventually, we should probably update the control with some of the functionality the Apple Version has like 3 columns support and overlay support. That'll be handy too when combined with the update waiting in PR #3173. We should probably have a separate issue tracking those features.

For now we'll just rename the control for 7.0