fix(CommandPalette): Results groups order based on initial groups order

[maximepvrt]

🔗 Linked issue

❓ 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

Currently, in CommandPalette, the order of groups is determined based on the processing type (search or useFuse) rather than maintaining the initial order of groups. This can lead to confusion and inconsistency, especially when users expect groups to remain in the order they were initially arranged.

To address this issue, I propose implementing a fix that ensures the order of groups is preserved based on their initial arrangement. By prioritizing the original order, users will have a more intuitive experience.

📝 Checklist

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

[benjamincanac]

I hear you but this was actually intended, the groups are computed in the order of the results so the command with the biggest score is on top.

[maximepvrt]

I understand your perspective, but it seems that maintaining the initial order of groups could enhance user experience, especially in scenarios where users anticipate consistency in group arrangement. Currently, however, it appears that Fuse results consistently precede group async search results. For instance, in UDashboardSearch, the theme group consistently returns as the top result when utilizing a group that utilizes search functionality.

While I acknowledge the intention behind prioritizing results based on score, it might be worth considering a balance where the initial order of groups is preserved, ensuring a more predictable and intuitive experience for users. Would it be possible to explore a solution that retains this balance?

[benjamincanac]

Of course I'm open to suggestions but your current implementation breaks the search on the documentation.

[maximepvrt]

@benjamincanac I propose to add a props which takes an array of string ['fuse', 'search', 'static'] to order the results. What do you think ? static for my other PR #1458