Renaming Material UI base form controls

I am going to rename components in vulcan-ui-material/lib/components/forms/base-controls/ because their names conflict with the style sheet names (used for Global theme overrides) of some core MUI components - for example MuiInput.

These components are actually not registered with registerComponent, only exported. This would be a breaking change for anyone who has built custom components based on them using import (our codebase at Etail21 has 6 such instances, for example).

Here are the proposed changes:

• MuiCheckbox => CheckboxBase
• MuiCheckboxGroup => CheckboxGroupBase
• MuiFormControl => FormControlBase
• MuiFormHelper => FormHelper
• MuiInput => InputBase
• MuiPicker => PickerBase
• MuiRadioGroup => RadioGroupBase
• MuiRequiredIndicator => RequiredIndicator
• MuiSelect => SelectBase
• MuiSuggest => SuggestBase
• MuiText => TextBase

Please let me know if you agree with this change or if you would like to suggest an alternative. Thanks!

[ErikDakoda]

@eric-burel It is a good idea to test new and more efficient patterns for Vulcan, and once a workable solution is implemented, tested and documented, to roll it out to the community. In the meantime, though, we have existing apps with tens of thousands of lines of code using current patterns that drew us to Vulcan in the first place. I think it’s legitimate to make improvements to existing code using those older patterns.

I am only suggesting adding registerComponent for these components at all because I will be touching the code anyway and these are the only components in the entire vulcan:ui-material that don’t use that pattern.

I don’t think that contradicts possibly moving away from registerComponent in the future.

[ErikDakoda]

This was implemented in PRs #2665 and #2666