Implement aliasing system

[yogeshgalav]

Implement aliasing system

[VividLemon]

In my point of view, "internal aliasing" is just bloat. I have mixed feelings about adding official aliased names and instead would prefer a system where users could maintain their own sets of aliases.

[VividLemon]

Related:
#1607
#1569

[yogeshgalav]

@VividLemon Implementing external alias and exporting internal alias is different thing,
I think this project replaces bootstrap-vue with minimum code change.
If the goal I mention I true, then exporting BInput should be first priority.

and creating alias system for better developer experience is other thing.
There's difference between features which are essential, and which improve product quality.

[xvaara]

IMHO, if it's just one search and replace on the codebase, I don't think we need to worry about this. Just document the change to a migration guide.

or something like:

import {BFormInput} from 'bootstrap-vue-next'
app.component('BInput', BFormInput)

[yogeshGroony]

@VividLemon Just wanted to save time and effort to change lot of codebase.
Please do it, from product point of view it would be great.
If you don't want to make internal alias, then you can keep short ones
Like everyone will prefer BInput over BFormInput
From product point please make the change,
there is no other alternate available for bootstrap-vue in market.

[VividLemon]

I was thinking about the purpose of the internal alias the other day, and came to the realization that it's a bit silly not to include it by default, as there isn't much of a downside... It doesn't necessarily need to be a default, but could be an opt in feature (one that would hopefully require a simple one line change perhaps). Or simply just be made the default. That being said, the inclusion of default aliases would also require the ability to add custom aliases. So, in conclusion, once I finish the alias system, I will include plans for default aliases.