Crate helixforge_core

Expand description

Shared data types: the catalog tree of tabs, groups and entries, and the actions an entry performs. Nothing here touches the system.

Modules§

search: Fuzzy search over entries: how well a query matches an entry’s name, id and description, so results can be ranked with the best match first.

Detect: The packages and command that show a non-package entry’s software.
Entry
Group
Identity: What an entry installs, from its package action or its detect table.
Needs: What an entry needs from the machine beyond its tools.
PackageNames: Package names per family; a missing family means the entry is not available there.
Precondition: A condition that hides an entry on machines it does not apply to.
Tab

Action: What an entry does when run: the operation model shared by every interface. The engine turns these into explicit plans.
Check
Item
NativeAction
NixAction
PackageManager: The package manager families that package entries can name.
Risk: How much an entry can affect the system, derived from its flags.

printable: Text from outside HelixForge (journal lines, file and unit names, error messages) made safe to show in a terminal: control characters, which could start escape sequences, become ?; tabs become spaces.
privileged: Whether an entry needs elevated privileges, from its flags and kind.
valid_binary_name: An executable name to look for on the PATH, including Flatpak export names such as org.gnome.meld.
valid_flatpak_id: A Flatpak application id: at least three dot-separated parts of letters, digits, hyphens and underscores.
valid_id: Entry, group and tab identifiers: lowercase, digits and hyphens.
valid_package_name: Reject values that could become flags or shell syntax in a command line.
valid_script_segment: One directory or file name in a script id: lowercase, digits, hyphens and underscores, as the scripts carried over from Linutil are named.