8000 docs(BProgress): Parity pass by dwgray · Pull Request #2689 · bootstrap-vue-next/bootstrap-vue-next · GitHub
[go: up one dir, main page]
Skip to content

docs(BProgress): Parity pass #2689

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
May 11, 2025
Merged

docs(BProgress): Parity pass #2689

merged 2 commits into from
May 11, 2025

Conversation

dwgray
Copy link
Member
@dwgray dwgray commented May 9, 2025 •
edited by coderabbitai bot
Loading

Describe the PR

  • Refactors the examples out of the docs and filled in the docs
  • Updated the component reference for BProgress and BProgressBar
  • Updated the parity spreadsheet
  • Verified the migration guide (the only deprecation was the v-html prop, which I'd already covered)

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

Summary by CodeRabbit

  • New Features

    • Added multiple new demo components showcasing various progress bar features, including basic usage, custom labels, multiple bars, different backgrounds, widths, heights, striped and animated styles.

  • Documentation

    • Updated and reorganized the progress component documentation for improved clarity and usability.
    • Replaced inline code examples with embedded interactive demos.
    • Enhanced descriptions for progress component properties and slots.
8000

@bolt-new-by-stackblitz Bolt.new (by StackBlitz)
Copy link

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

@coderabbitai coderabbitai
Copy link
coderabbitai bot commented May 9, 2025 •
edited
Loading

Walkthrough

This update introduces several new Vue demo components showcasing various features of progress bars, such as custom labels, multiple bars, different heights, widths, backgrounds, and animations. The progress component documentation is refactored to use these new demos via embedded references, and the data file for progress components receives enhanced descriptive fields and structural improvements for clarity and maintainability.

Changes

File(s) Change Summary
apps/docs/src/data/components/progress.data.ts Added detailed description fields to all props, updated slot descriptions, and replaced explicit common prop declarations with a dynamic utility function for prop inclusion.
apps/docs/src/docs/components/demo/ProgressBasic.vue
apps/docs/src/docs/components/demo/ProgressAnimated.vue
apps/docs/src/docs/components/demo/ProgressBackgrounds.vue
apps/docs/src/docs/components/demo/ProgressCustomLabels.vue
apps/docs/src/docs/components/demo/ProgressHeight.vue
apps/docs/src/docs/components/demo/ProgressLabels.vue
apps/docs/src/docs/components/demo/ProgressMultipleBars.vue
apps/docs/src/docs/components/demo/ProgressStriped.vue
apps/docs/src/docs/components/demo/ProgressWidth.vue		 Added new Vue demo components, each illustrating a specific progress bar feature (basic, animated, backgrounds, custom labels, height, labels, multiple bars, striped, width). Each component is presentational with no script logic.
apps/docs/src/docs/components/progress.md Refactored documentation to use embedded demo components via <<< DEMO syntax, reorganized and clarified textual content, removed inline code and custom wrappers, and updated section flow and notes for improved clarity.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DocsPage
    participant DemoComponent

    User->>DocsPage: Navigates to Progress documentation
    DocsPage->>DemoComponent: Loads embedded demo (e.g., ProgressBasic)
    DemoComponent-->>DocsPage: Renders progress bar example
    DocsPage-->>User: Displays documentation with live demos
Loading

Poem

In the warren where code bunnies leap,
New demos and docs now run deep!
Progress bars twinkle 8000 , striped and wide,
With labels and colors, they're shown with pride.
Hop along, explore each new view—
The docs are refreshed, and the carrots are too! 🥕

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@pkg-pr-new pkg.pr.new
Copy link
pkg-pr-new bot commented May 9, 2025

bsvn-vite-ts

npm i https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next@2689

npm i https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next/@bootstrap-vue-next/nuxt@2689

commit: 6c7b390

coderabbitai[bot]
coderabbitai bot reviewed May 9, 2025
View reviewed changes
Copy link
@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (5)
apps/docs/src/docs/components/progress.md (5)

5-6: Refine introductory text for clarity
The current intro reads as a bit generic and repeats “progress bars.” Consider explicitly naming the component (e.g., BProgress) and tightening the phrasing.

18-18: Clarify wording and spelling

  • “in a single process” is confusing; perhaps “in a single progress instance” or similar.
  • Use “subcomponents” (one word) for consistency with other docs.
  • Add a period at the end of the sentence.
🧰 Tools
🪛 LanguageTool

[misspelling] ~18-~18: This word is normally spelled as one.
Context: ...e prop on the individual BProgressBar sub-components (see the [Multiple Bars](#multiple-bars...

(EN_COMPOUNDS_SUB_COMPONENTS)

28-28: Unify phrasing and spelling in custom label guidance

  • Change “sub-component” → “subcomponent” for consistency.
  • Consider rephrasing to “Use the def 8000 ault slot of a BProgressBar subcomponent or the label prop to customize the label.”
🧰 Tools
🪛 LanguageTool

[misspelling] ~28-~28: This word is normally spelled as one.
Context: ...he default slot within a BProgressBar sub-component, or by using the label property on `B...

(EN_COMPOUNDS_SUB_COMPONENT)

34-36: Fix typo in width description
“maximum with of its parent container” → “maximum width of its parent container.”

75-77: Improve list-item consistency

  • Capitalize first words (“Height, if specified…” → “Height: if specified…”).
  • Consider adding or removing periods uniformly at the end of each bullet.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ce869f0 and 6c7b390.

📒 Files selected for processing (11)
  • apps/docs/src/data/components/progress.data.ts (3 hunks)
  • apps/docs/src/docs/components/demo/ProgressAnimated.vue (1 hunks)
  • apps/docs/src/docs/components/demo/ProgressBackgrounds.vue (1 hunks)
  • apps/docs/src/docs/components/demo/ProgressBasic.vue (1 hunks)
  • apps/docs/src/docs/components/demo/ProgressCustomLabels.vue (1 hunks)
  • apps/docs/src/docs/components/demo/ProgressHeight.vue (1 hunks)
  • apps/docs/src/docs/components/demo/ProgressLabels.vue (1 hunks)
  • apps/docs/src/docs/components/demo/ProgressMultipleBars.vue (1 hunks)
  • apps/docs/src/docs/components/demo/ProgressStriped.vue (1 hunks)
  • apps/docs/src/docs/components/demo/ProgressWidth.vue (1 hunks)
  • apps/docs/src/docs/components/progress.md (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
apps/docs/src/data/components/progress.data.ts (2)
apps/docs/src/utils/index.ts (2)
  • pick (4-4)
  • buildCommonProps (3-3)
apps/docs/src/types/index.ts (1)
  • PropertyReference (11-16)
🪛 LanguageTool
apps/docs/src/docs/components/progress.md

[misspelling] ~18-~18: This word is normally spelled as one.
Context: ...e prop on the individual BProgressBar sub-components (see the [Multiple Bars](#multiple-bars...

(EN_COMPOUNDS_SUB_COMPONENTS)

[misspelling] ~28-~28: This word is normally spelled as one.
Context: ...he default slot within a BProgressBar sub-component, or by using the label property on `B...

(EN_COMPOUNDS_SUB_COMPONENT)

[misspelling] ~70-~70: This word is normally spelled as one.
Context: ...e bars Include multiple BProgressBar sub-components in a BProgress component to build a h...

(EN_COMPOUNDS_SUB_COMPONENTS)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build
🔇 Additional comments (39)
apps/docs/src/data/components/progress.data.ts (19)

3-3: Adopt DRY by importing common prop helpers
Great addition of buildCommonProps and pick to centralize and reuse common prop metadata instead of repeating throughout multiple components.

12-16: Clarify animated behavior
The new description clearly explains that setting animated also applies striped, which will help users understand the side effect.

20-22: Document height override
Good detail on how to override the default height using any valid CSS unit.

26-27: Specify max prop purpose
The description “Set the maximum value” concisely conveys the intent of the max prop.

30-31: Explain precision rounding
Showing that this controls the number of decimal places will help avoid confusion.

35-36: Detail showProgress output
Clear explanation that this toggles percentage display.

40-41: Clarify showValue display
Explicitly stating it shows the raw value improves discoverability of the feature.

45-47: Define striped styling
Good to note this prop simply enables the striped background.

50-52: Describe value control
The description “The current value of the progress bar” is straightforward and helpful.

53-53: Integrate common visual props
The spread of ['bgVariant','textVariant','variant'] from common props is an excellent DRY improvement—keeps docs consistent and maintainable.

71-73: Enhance animated description in BProgressBar
Consistent with the parent component, noting the striped side‐effect here is very helpful.

76-78: Document explicit label override
Clear guidance for when and how to use the label prop.

81-83: Clarify max usage in BProgressBar
Matching the max description with the top‐level component keeps behavior expectations aligned.

86-88: Explain decimal precision
Specifying default of 0 and its effect on rounding is great for users.

91-93: Detail showProgress toggle
Good to mirror the BProgress semantics here for consistency.

96-98: Clarify raw value display
Reiterating that showValue shows the raw number is helpful and consistent.

101-103: Define striped style
This matches the top‐level component’s description—pleasant consistency.

106-108: Describe bar value prop
Clear and aligned with the parent component.

109-109: Apply common visual props to BProgressBar
Great use of pick(buildCommonProps(), ...) to keep bar‐specific props in sync with the main component.

apps/docs/src/docs/components/demo/ProgressHeight.vue (1)

3-4: Simple height demo is clear and concise
This component effectively demonstrates varying heights on BProgress. Assuming global registration of BProgress, no additional imports are needed.

apps/docs/src/docs/components/demo/ProgressBackgrounds.vue (1)

3-6: Background variant showcase is spot on
Nicely illustrates the different variant options with consistent spacing.

apps/docs/src/docs/components/demo/ProgressAnimated.vue (1)

3-6: Animated and striped demo is correct
Demonstrates combined striped + animated props across variants well.

apps/docs/src/docs/components/demo/ProgressBasic.vue (1)

3-7: Basic progress states rendered properly
Clear progression from 0% to 100% with proper spacing—exactly what the basic demo needs.

apps/docs/src/docs/components/demo/ProgressStriped.vue (1)

1-9: All set for striped demo
The ProgressStriped.vue component correctly demonstrates striped progress bars with appropriate variants and spacing. Region markers and markup are consistent with project conventions.

apps/docs/src/docs/components/demo/ProgressWidth.vue (1)

1-11: Width demo is correct
The ProgressWidth.vue component effectively showcases default and custom width classes. Template structure and region markers are consistent.

apps/docs/src/docs/components/demo/ProgressLabels.vue (1)

1-15: Label display demo looks good
ProgressLabels.vue accurately demonstrates value and progress label options with precision control. Markup and props usage are clear and consistent.

apps/docs/src/docs/components/demo/ProgressMultipleBars.vue (1)

1-9: Multiple bars demo is correct
ProgressMultipleBars.vue properly uses a parent BProgress with BProgressBar children to illustrate segmented bars. Structure and region tags are in line with other demos.

apps/docs/src/docs/components/progress.md (12)

12-12: Demo embed for Basic Usage looks good
The <<< DEMO ./demo/ProgressBasic.vue directive correctly references the standalone demo component.

24-24: Demo embed for Labels section looks good
The <<< DEMO ./demo/ProgressLabels.vue directive is properly configured.

30-30: Demo embed for Custom Labels looks good
The <<< DEMO ./demo/ProgressCustomLabels.vue directive correctly references the demo.

32-32: Width section header placement is correct
Reordering “Width” before “Height” matches the logical flow of props.

38-38: Demo embed for Width looks good
The <<< DEMO ./demo/ProgressWidth.vue directive is correctly set.

44-44: Demo embed for Height looks good
The <<< DEMO ./demo/ProgressHeight.vue directive is properly referenced.

50-50: Demo embed for Backgrounds looks good
The <<< DEMO ./demo/ProgressBackgrounds.vue directive is correct.

52-52: Striped Background header is clear
Moving and renaming this section improves discoverability of the striped variant.

56-56: Demo embed for Striped Background looks good
The <<< DEMO ./demo/ProgressStriped.vue directive is correctly configured.

62-62: Demo embed for Animated Background looks good
The <<< DEMO ./demo/ProgressAnimated.vue directive is properly referenced.

64-66: Animated info note is accurate
The note that animated implies striped is clear and helpful.

72-72: Demo embed for Multiple Bars looks good
The <<< DEMO ./demo/ProgressMultipleBars.vue directive correctly references the multi-bar demo.

@VividLemon VividLemon merged commit 070cb8c into bootstrap-vue-next:main May 11, 2025
5 checks passed
xvaara added a commit to xvaara/bootstrap-vue-next that referenced this pull request May 14, 2025
@xvaara
Merge remote-tracking branch 'upstream/main'
c0a00ac 
* upstream/main:
  chore: release main (bootstrap-vue-next#2690)
  docs(BProgress): Parity pass (bootstrap-vue-next#2689)
  fix(BTableSimple): fixed and nobordercollapse to work fixes bootstrap-vue-next#2685
  docs: fix incorrect references and missed script sections (bootstrap-vue-next#2686)
  docs: implement on this page expand/collapse with useScrollspy (bootstrap-vue-next#2679)
  chore: release main (bootstrap-vue-next#2683)
  feat(BTable): implement 'fixed' and 'noBorderCollapse' props (bootstrap-vue-next#2681)
  chore: release main (bootstrap-vue-next#2678)
  Update package.json
  fix(BFormSelect): prevent options with label from being treated as groups (bootstrap-vue-next#2666)
  fix: patch regression issue in bootstrap-vue-next#2665 (bootstrap-vue-next#2670)
  Update release-main.yaml
  chore: release main (bootstrap-vue-next#2660)
  chore: update depencies
  fix(BTabs): corrent classes on ssr (bootstrap-vue-next#2664)
  Changes to public composables (bootstrap-vue-next#2425)
  docs(BTable): parity pass (bootstrap-vue-next#2669)
xvaara pushed a commit to unstoppablecarl/bootstrap-vue-next that referenced this pull request May 22, 2025
@dwgray @xvaara
docs(BProgress): Parity pass (bootstrap-vue-next#2689)
362ce6f
xvaara added a commit to unstoppablecarl/bootstrap-vue-next that referenced this pull request May 22, 2025
@xvaara
Squashed commit of the following:
571c67d 
commit 2a9e30b
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Thu May 15 18:24:07 2025 +0300

    doc data

commit 08c89fd
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Thu May 15 17:57:29 2025 +0300

    feat(BPopover): add titleClass and bodyClass, remove unneeded customClass prop since class is inherited to the same place

commit 90b578d
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Wed May 14 11:39:42 2025 +0300

    feat(BToast): add noProgress prop, make progress show as default if modelValue is number. fix(useToastController): if using the deprecated show method the countdown didn't start.

commit dc85d94
Author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Date:   Sun May 11 09:53:25 2025 -0500

    chore: release main (bootstrap-vue-next#2690)

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

commit 070cb8c
Author: David W. Gray <dwgray67@hotmail.com>
Date:   Sun May 11 07:52:30 2025 -0700

    docs(BProgress): Parity pass (bootstrap-vue-next#2689)

commit c61f532
Author: Thierry Blind <tbl0605@gmail.com>
Date:   Sun May 11 16:52:14 2025 +0200

    fix(BTableSimple): fixed and nobordercollapse to work fixes bootstrap-vue-next#2685

commit beae36f
Author: David W. Gray <dwgray67@hotmail.com>
Date:   Sun May 11 07:43:58 2025 -0700

    docs: fix incorrect references and missed script sections (bootstrap-vue-next#2686)

commit 34432d9
Author: David W. Gray <dwgray67@hotmail.com>
Date:   Sun May 11 07:42:02 2025 -0700

    docs: implement on this page expand/collapse with useScrollspy (bootstrap-vue-next#2679)

commit ce869f0
Author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Date:   Wed May 7 11:16:08 2025 -0500

    chore: release main (bootstrap-vue-next#2683)

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

commit 9486276
Author: Mohamed Nasri <51300752+mhn147@users.noreply.github.com>
Date:   Wed May 7 09:44:38 2025 -0600

    feat(BTable): implement 'fixed' and 'noBorderCollapse' props (bootstrap-vue-next#2681)

commit a4a9294
Author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Date:   Mon May 5 09:16:09 2025 -0500

    chore: release main (bootstrap-vue-next#2678)

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

commit 0165e94
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Mon May 5 16:24:04 2025 +0300

    Update package.json

commit c1645a9
Author: Rajitha <rajithaeye@gmail.com>
Date:   Wed Apr 30 23:49:23 2025 +0530

    fix(BFormSelect): prevent options with label from being treated as groups (bootstrap-vue-next#2666)

commit 59ddc39
Author: Thierry Blind <tbl0605@gmail.com>
Date:   Wed Apr 30 20:17:34 2025 +0200

    fix: patch regression issue in bootstrap-vue-next#2665 (bootstrap-vue-next#2670)

commit d82091b
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Wed Apr 30 06:01:10 2025 +0300

    Update release-main.yaml

commit 31cb4bf
Author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Date:   Wed Apr 30 04:51:31 2025 +0300

    chore: release main (bootstrap-vue-next#2660)

    Co-Authored-By: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

commit 6733770
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Wed Apr 30 05:15:02 2025 +0300

    chore: update depencies

commit 2b37c18
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Wed Apr 30 04:36:46 2025 +0300

    fix(BTabs): corrent classes on ssr (bootstrap-vue-next#2664)

    fix(BTabs): corrent classes on ssr
    fix(BTabs): fix another recursion error

commit 99718eb
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Wed Apr 30 04:20:00 2025 +0300

    Changes to public composables (bootstrap-vue-next#2425)

    feat(BAlert)!: make act like toast, useShowHide.
    feat(useShowHide): create triggerRegistry for adding external triggers (like in vBToggle)
    fix: type popoverController
    fix(useShowHide): focustrap off at the begining of leave, pass down the trigger to other hide emits.
    fix(vBToggle): keep track of targets
    fix(BPopover)!: change prop content to body to align with other components
    fix(BTooltip)!: change prop content to body to align with other components
    feat(usePopoverController): allow more options
    fix(vBToggle): find late components, ie. inside ClientOnly
    fix(useModalController)!: move props to main level, add slots
    feat(usePopoverController): add slots
    feat(useToastController)!: remove props obj, the parameters are flat now. Add slots, rename pos -> position
    feat(useShowHide): show returns a promise, resolve on show or hide.
    feat(useToggle): toggle any show/hide component
    feat!: controller composables functions return promise, with chainable functions
    feat(useModalController): add support for using syntax in ts
    feat(BModal): add okClass and cancelClass to add classes to the buttons.
    feat(useModalController)!: change of api, check the docs
    fix: inline functional style to show toast,modal and dropdown
    feat(useToggle): add trigger to promise resolve on hide.
    fix(BCarousel): fix v-for updates

commit 340edfd
Author: David W. Gray <dwgray67@hotmail.com>
Date:   Mon Apr 28 18:39:44 2025 -0700

    docs(BTable): parity pass (bootstrap-vue-next#2669)

commit 4dd6c89
Author: Jukka Raimovaara <roska@mentalhouse.fi>
Date:   Mon Apr 28 22:46:31 2025 +0300

    fix(BDropdown): don't calulcate the position when dropdown is not shown.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

@VividLemon VividLemon VividLemon approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@dwgray @VividLemon
0