The Explorer

View as Markdown

This article describes the Explorer, the left-hand tree view of a Project. Use the Explorer when you want to move through a Project by name (file by file, Resource by Resource) rather than by topology. The Board shows the same Project as a graph; the Explorer shows it as a tree.

Resources are folders

Each Resource appears in the Explorer as a folder. Expanding a Resource shows the files in its Bucket directory: every Resource is backed by a directory in the Project’s Bucket, and the Explorer renders that directory tree directly.

The same files are reachable from the hyjal files command (hyjal files ls, get, put, rm). The Explorer is the visual counterpart.

Deploy artifacts live in the same Bucket, digest-named and read-only. They appear in the tree as read-only entries; you can open one to inspect it, but not edit it.

Files

Selecting a file opens it in the workspace. Text files open in an editor; .db files open as live Tables grids; static assets open in a preview. Opened files become tabs you can arrange and split.

Categories

The Explorer groups Resources by category (static sites, services, data directories) so a Project with many Resources stays legible. Categories are a grouping in the view; they do not change how a Resource is addressed or deployed. Collapse a category to focus on the Resources you are working on.

Search and filter

The search filter at the top of the Explorer narrows the tree to entries whose name matches what you type. It filters across Resources and files at once, so a query for orders surfaces both an orders Resource and an orders.sql file. Clear the field to restore the full tree.

Right-click operations

Right-clicking an entry opens a context menu. The available operations depend on what you clicked.

TargetOperations
Empty space / Project rootNew Resource, New file, New table
Resource folderNew file, New table, Rename, Delete
FileRename, Delete, Open
Table (.db)Open in Tables view, Rename, Delete

New Resource starts a Resource from the Explorer without leaving for the Board or the CLI; the new Resource appears as a folder and as a node on the Board. New table creates a Hyjal Table in the Project. Rename and delete apply to the selected entry.

Deleting a Resource removes its Bucket directory and its served endpoint. Deleting a file removes it from the Bucket. Neither is a deploy; both take effect immediately.

Next steps