-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement aliasing system #1753
Comments
@VividLemon Implementing external alias and exporting internal alias is different thing, and creating alias system for better developer experience is other thing. |
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. |
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) |
@VividLemon Just wanted to save time and effort to change lot of codebase. |
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. |
feat: implement global alias system fixes bootstrap-vue-next#1753 refactor: add bvn:: prefix to symbol keys refactor: fix typo in 'BCardImageProps' change to 'BCardImgProps'
… (bootstrap-vue-next#1889) feat: implement a use defaults system fixes bootstrap-vue-next#1607 feat: implement global alias system fixes bootstrap-vue-next#1753 refactor: add bvn:: prefix to symbol keys refactor: fix typo in 'BCardImageProps' change to 'BCardImgProps' feat(BFormInput)!: move props lazy, trim & number to v-model modifier. Modifiers should behave more like native Vue modifiers (number modifier with unparseable value returns value as is) feat(BFormInput): type number performs the same as modifier feat(BCarouselSlide): allow individual interval for slides chore: update deps to fix some issues (nuxt useId, vue-tsc etc) docs: global options, aliases feat(nuxt): automatically globally set teleportTo to `#teleports` feat(BreakpointProps)!: strongly type breakpoints. Instead of weak string | number => 1,2,3...'1','2','3'... refactor(BRow): use script setup instead of options api refactor(BCol): use script setup instead of options api
Clear and concise description of the problem
When migrating from bootstrap-vue to bootstrap-vue-next, one of the major problem which leads to major code change is
"BInput" component not present, this componen is present but with other name "BFormInput"
Goal: minimum code change while migrating from bootstrap-vue.
Benifit: less boiler plate for component name, less or no code change for migration
Suggested solution
The Alias for BFormInput should be BInput
just like Bootstrap-vue
This can be achieved with component.d.ts
Alternative
New component BInput which directly exports BFormInput
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: