Gabriel Bacha4k downloadsAdd Notion-style pill colors and conditional formatting to Base tables.
Bases Visuals adds compact, Notion-inspired pill colors and conditional formatting to Obsidian Base tables.
Plugin page · More Obsidian plugins · Gabriel Bacha's website · Request a feature
Open a Base table containing a list property. Values receive stable automatic colors as they appear.
file.name column, click the empty area of a filename cell to rename that file in place; the filename link itself still opens the note. Press Enter or leave the field to save, or press Escape to cancel. The file stays in its current folder with its original extension, and duplicate or invalid names are rejected safely.Pill colors are scoped to the current Base and shared by its views. Base-wide choices are stored once in a sparse top-level basesVisuals block, while automatic values are discovered in memory and never written. Unknown extension fields and newer schema versions are preserved so another compatible editor can safely share the same block. Concurrent edits to different fields are merged; incompatible edits to the same field are left unsaved and reported instead of being overwritten. Friendly column names are display-only: settings remain attached to the underlying note property even when a Base renames the column. Conditional-formatting rules can target only the current view or every view in the Base, remain case-insensitive, and are evaluated top-to-bottom. Color and conditional-formatting changes never modify existing note properties; the group + action creates a new note with the selected list value. Layout actions use Obsidian's native Base view configuration. Shared appearance lives in basesVisuals; view-only rules and column appearance live in basesVisualsView. Column appearance is shared across every view in the Base by default; turn off All views in this base to create a view-specific override. The explicit Remove from row action delegates that one list edit to Obsidian.
Smart strategies recognize common property families such as status, state, workflow, phase, priority, severity, and suffixed forms such as status_todo or sprint_priority. Ordered labels and explanatory suffixes are normalized, so values such as 2. In Progress, 3.Waiting (for a dependency), and 1.P0 retain their semantic colors.
Bases Visuals is being prepared for the Obsidian Community Plugins directory. Once accepted, install it from Settings → Community plugins → Browse.
main.js, manifest.json, and styles.css from the latest GitHub release.<vault>/.obsidian/plugins/bases-pill-colors/..base file; view-specific choices remain with that view.npm install
npm run dev
Use npm run build, npm test, and npm run lint before releasing.
Report bugs and request features through GitHub Issues.
Plugin page · More Obsidian plugins · Gabriel Bacha's website · Request a feature
src/generated/portable-names.ts is a compatibility copy of canonical contract v2 Applications-GB/_Supporting/bases-contract-NPM/src/names.ts. The normal plugin build imports this file for rename behavior; other contract imports retain the registry dependency. Run node scripts/filename-contract.mjs --update after validating a canonical change. The build checks the pinned SHA-256, and checks canonical drift when that checkout is present. A standalone clone can build using its checksum-pinned copy. Do not hand-edit the generated helper.
BPC_BUILD_DIR directs a development bundle to an isolated output folder. The native acceptance test uses the existing strict Obsidian harness with a generated vault/profile, the installed executable and code-only ASAR. It verifies artifact, user-data and vault ownership and closes only its owned processes. The supplemental source-rule layout fixture uses SDK test stubs; the ordinary plugin and real popout are loaded normally. No installed plugin, existing profile or personal vault is changed.
Clean unused checks cached Markdown note properties across the vault, which includes notes hidden by another Base filter. It keeps declared options and uncertain properties, lists the proposed removals and checks their usage again at confirmation. Unindexed notes prevent removal. A failed close-time save keeps its dirty data for retry; it is not silently discarded. The Obsidian void unload hook cannot delay operating-system application exit.
The immutable source files in tests/baseline/ are the performance reference recorded by provenance.json; they are not maintained as a second implementation. Comparisons use named synthetic sizes and the same host. They do not establish a maximum supported table or an absolute response-time target.
Scoped settings capture the Base file and native view when an edit starts. If Obsidian reuses a pane for another file or view, the old store completes its queued write against the original target and a new store reads the new target. Save results belong to their store, so a late result cannot overwrite the new pane's feedback.