Base filtering UI loses awareness of implicit field types when there are no notes in main view

Bug reports
1

Steps to reproduce

  1. Open the sandbox vault.
  2. Disable all core plugins except Bases.
  3. In the Welcome note, right click and choose to insert a new base via the context menu.
  4. Open the base in its own tab.
  5. Move the base tab to the left sidebar.
  6. Close the welcome note if you still have it open.
  7. In the base in the sidebar, attempt to use the ui to create a contains filter for the built-in name field.
  8. Notice that the field type icon indicates the type is unknown, and your only options for the condition are about exact equality and existence. Conditions such as “contains” which should be available for a string property are not available.

Did you follow the troubleshooting guide? [Y/N]

Yes.

Expected result

The functionality for configuring a base should work correctly regardless of whether there are notes open in the main view or not.

Actual result

Some functionality of the base filtering does not exist, and it seems that base becomes unable to recognize the types of built-in fields.

Environment

SYSTEM INFO:
Obsidian version: 1.12.7
Installer version: 1.12.7
Operating system: Windows 11 Home 10.0.26200
Login status: not logged in
Language: en-GB
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on

RECOMMENDATIONS:
none

Additional information

If the base file is in the main view rather than a side panel, it works correctly. As soon as something is in the main view, the issue stops happening.