fix(Breadcrumb): use active property if defined, fallback on last item otherwise

[noook]

🔗 Linked issue

Resolves: #4642

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Property active for active breadcrumb was ignored.

Change && logical operator to ?? to better handle the behavior:

• If active is set to false, item is not active
• If active is set to true, item is active
• If active is not defined, or null, the last item will be considered as active.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[benjamincanac]

@noook I'm not sure this is correct, the active is always false here since it's injected from the ULink slot props 🤔

[noook]

Sorry for the delay, and I see the issue.

I don't know how to properly fix this. The last item should only be considered active if none of the previous items was marked as active.

Maybe Breadcrumbs could benefit from a prop 'last-active?': boolean that checks for index === items!.length - 1 only if this prop is set to true (default true to prevent breaking changes) ?

<UBreadcrumps :last-active="false" ... /> In combination with active: true on a BreadcrumbItem, would achieve the desired output.

[benjamincanac]

Closing in favor of cc8cbf3.