Description

Fixes an issue introduced in v0.40.0 where modals created with useModal().create() were not displaying titles defined in the component itself.

Problem

When using useModal with a custom component that defines its own title prop, the title would not display:

<!-- MyModal.vue -->
<template>
  <BModal title="My title">This is a modal.</BModal>
</template>

<!-- Calling component -->
<script setup>
import { useModal } from 'bootstrap-vue-next';
const { create } = useModal();
const showModal = () => create({ component: MyModal }).show();
</script>

The title "My title" would not appear in the rendered modal. However, if the title was passed directly to create({ title: "My title" }), it would display correctly.

Root Cause

In orchestratorShared.ts, the buildPromise function's set method was unconditionally setting title and body properties to their resolved values, even when they were undefined. This caused undefined values to override the component's own prop definitions.

Solution

Modified the set method to only include title and body in the store update if they are explicitly defined and not undefined. This allows component-defined props to take precedence when no override is provided.

Changes

• Updated packages/bootstrap-vue-next/src/composables/orchestratorShared.ts to conditionally set title and body properties
• Added comprehensive tests in packages/bootstrap-vue-next/src/composables/orchestratorShared.spec.ts to verify the fix

Testing

• ✅ All existing tests pass (1633 tests)
• ✅ New tests verify title/body behavior
• ✅ Build successful
• ✅ Linting passes

Closes #[issue number]

Fixes #2877

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.