BladeItem should be BladeViewItem to be consistent with typical naming conventions

[michael-hawker]

Describe the bug

Most container controls follow the pattern of ____View and ____ViewItem for children. Currently we have BladeView but BladeItem instead of BladeViewItem.

Should we fix this for 7.0? Do we want to make this a complete break or figure out a transition scenario?

[michael-hawker]

I think that may be our only case, but we may want to check other controls...

[michael-hawker]

@RosarioPulella thoughts on this? Are there any others we've missed?

Are there other patterns where we're already consistent?

[Rosuavio]

Still combing threw, but I noticed that the _____Layouts have ____Layout and _____Item. I don't know if this is desired pattern, if it effects our ____Views or vice-versa?

[Rosuavio]

Interestingly, if you take a control like Carousel, that does not have a View in there name, it just has CarouselPanel and CarouselItem, would arguing for changing BladeItem to BladeViewItem mean we should also change CarousleItem to CarouslePanelItem?

I guess one difference between these controls is how we colloquially talk about these controls and how they are documented. Assuming that we refer to these controls as "BladeView" and "Carousle", then CarousleItem can make sense but BladeItem does not.

Personally saying "BladeView" seems more natural than "Blade" when referring to this control.

[michael-hawker]

Carousel is a bit of an odd example as it's an ItemsControl but also has a custom Panel which is kind of tied specifically to it. So the ____ + _____Item pattern still holds with that as Carousel is the main parent item vs. the child CarouselItem.

I think BladeView and BladeItem vs BladeViewItem is the outlier. Think the main question is if we want to change it as the only outlier to break things just for consistency moving forward...