8000 perf: use a composable rather than BTransition component, eliminating… by VividLemon · Pull Request #2372 · bootstrap-vue-next/bootstrap-vue-next · GitHub
[go: up one dir, main page]

Skip to content

perf: use a composable rather than BTransition component, eliminating… #2372

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

Merged
merged 1 commit into from
Nov 21, 2024

Conversation

VividLemon
Copy link
Member

… a useless fragment

Describe the PR

A clear and concise description of what the pull request does.

Small replication

A small replication or video walkthrough can help demonstrate the changes made. This is optional, but can help observe the intended changes. A mentioned issue that contains a replication also works.

PR checklist

What kind of change does this PR introduce? (check at least one)

  • Bugfix 🐛 - fix(...)
  • Feature - feat(...)
  • ARIA accessibility - fix(...)
  • Documentation update - docs(...)
  • Other (please describe)

The PR fulfills these requirements:

  • Pull request title and all commits follow the Conventional Commits convention or has an override in this pull request body This is very important, as the CHANGELOG is generated from these messages, and determines the next version type. Pull requests that do not follow conventional commits or do not have an override will be denied

Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link
pkg-pr-new bot commented Nov 21, 2024

Open in Stackblitz

pnpm add https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next@2372
pnpm add https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next/@bootstrap-vue-next/nuxt@2372

commit: 2261ade

@VividLemon VividLemon merged commit a788a2d into bootstrap-vue-next:main Nov 21, 2024
4 checks passed
@github-actions github-actions bot mentioned this pull request Nov 21, 2024
@xvaara
Copy link
Contributor
< 8000 div> xvaara commented Nov 21, 2024

@VividLemon I'm against this... adding css again, css that doesn't even use bootstrap variables.

@VividLemon
Copy link
Member Author

@VividLemon I'm against this... adding css again, css that doesn't even use bootstrap variables.

BTransition consumed components already use this CSS anyways. There is no real difference between before/after this change besides eliminating BTransition from the codebase

It could be a good idea to refactor to use actual bootstrap classes, if at all possible. But on the other hand to that, Transition is a useful abstraction for managing transitions

xvaara added a commit to xvaara/bootstrap-vue-next that referenced this pull request Nov 22, 2024
* upstream/main:
  chore: release main (bootstrap-vue-next#2371)
  perf: use a composable rather than BTransition component, eliminating a useless fragment (bootstrap-vue-next#2372)
  better fix for the hidden on reference out of view. (bootstrap-vue-next#2370)
  revert release-please upgrade
  Update release-please to v4
  better fix for the hidden on reference out of view. (bootstrap-vue-next#2369)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0