feat(sidebar): filter both databases and collections with dot notation

[ooorayray]

Description

Updates the sidebar filter to allow filtering both databases and collections by dot notation: "."

Screen.Recording.2025-05-11.at.3.13.17.AM.mov

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• If this change updates the UI, screenshots/videos are added and a design review is requested
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

When there are many databases with the same set of collections (think multi-tenancy), filtering by either databases or collections is insufficient. Filtering on both allows one to access a specific database and collection quickly.

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[harris]

This is amazing! Thanks @ooorayray !!!

[kraenhansen]

While this works, the . has special meaning in the regular expression and I believe it should be escaped here to capture the intent of the change, to mean a literal "." (dot).

Suggested change

	regex: new RegExp('ready_1_1.coll_ready_shared_name', 'i'), // this matches only coll_ready_shared_name collection in ready_1_1 database
	regex: new RegExp('ready_1_1\.coll_ready_shared_name', 'i'), // this matches only coll_ready_shared_name collection in ready_1_1 database

[ooorayray]

Fixed!

[kraenhansen]

Thanks for your contribution - it looks good to me 👍 I wonder if it would make sense (in this PR or a follow-up) to do the same for filterDatabases by passing in the connectionName too and have that propagate into filterDatabases as well.

[ooorayray]

Thanks for your contribution - it looks good to me 👍 I wonder if it would make sense (in this PR or a follow-up) to do the same for filterDatabases by passing in the connectionName too and have that propagate into filterDatabases as well.

Perhaps this would make more sense in the follow-up. I took a stab at this but it seems more involved: for example, would we allow . as a valid filter?

[ooorayray]

Hi @kraenhansen, please let me know if there are any other blockers for this PR that I can help resolve. Thanks!

[gribnoysup]

Hey @ooorayray! Thanks for the contribution, sorry for the delay on getting back to you on this. Change looks good to me and I just kicked off our CI to make sure that all the existing tests are passing and don't need to be adjusted.

[gribnoysup]

Seems like we're missing some permissions for smoketests to run for external contribs, but otherwise CI is green, so I'll merge. @ooorayray thanks again for the contribution, very nice change to the search logic! It should get into the next release