dirsql 0.4.98 → 0.4.100

package/docs/reference/config.md

@@ -47,13 +47,12 @@ ignore = ["node_modules/**", ".git/**"]
 
 ### Glob rule
 
-Every glob in dirsql — `ignore`, a `[[table]]`'s `glob`, and a
-[path-table](./path-tables.md#writing-the-path) — reads as the shell does:
-`*` and `?` match within one path segment and never cross `/`; `**` matches
-any depth. So `ignore = ["*"]` hides only the files directly inside the root,
-`ignore = ["build/*"]` hides `build/a.o` but not `build/sub/b.o`, and
-`glob = "*.json"` selects only the top-level `.json` files; write
-`**/*.json` to select them at every depth.
+Every glob in dirsql, whether `ignore`, a `[[table]]`'s `glob` or a
+[path-table](./path-tables.md#writing-the-path), reads as bash does with
+`globstar` on. The [glob page](./glob.md) has the rules, examples and every
+divergence. In short, `*` and `?` stay within one path segment, `**` crosses
+directories, and `glob = "*.json"` selects only top-level `.json` files; write
+`**/*.json` for every depth.
 
 Persistence is not a config key. Keep the SQLite index on disk between runs
 with the [`--persist [PATH]` CLI flag](./cli.md#dirsql-server) — a machine-local
@@ -232,7 +231,7 @@ what its required `on-file` command emits — dirsql injects nothing (see
 |---|---|---|
 | `name` | yes | The table's SQL name — the name you query it by. Declared, never derived from `ddl`: dirsql does not read the DDL text. The `ddl` must create a table by this name; if it doesn't, loading fails. |
 | `ddl` | yes | A SQL batch, run verbatim — any number of statements. It must create a table called `name`; that table holds the file rows, and only the columns it declares are kept (keys the `on-file` command emits that are not declared are dropped). The rest of the batch is yours: indexes, virtual tables, triggers. See [Batch `ddl`](#batch-ddl). |
-| `glob` | yes | Glob pattern, [anchored](#glob-anchor) at the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
+| `glob` | yes | Glob pattern, [anchored](#glob-anchor) at the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` is a literal, as in bash and a path-table; the [glob page](./glob.md) has the syntax. |
 | `on-file` | **yes** | A command run once per table, with every matched file's absolute path appended as a trailing argument; its stdout (one JSON array of row objects) is the table's rows. Must be non-empty. A `[[table]]` with no `on-file` is a load error (see [parse errors](#parse-errors)). See [Command hooks](./hooks.md#on-file). |
 | `strict` | no (default `false`) | When `true`, rows whose keys do not exactly match the declared columns are rejected with an error: extra keys error, and every declared column must be supplied by the `on-file` output. When `false`, extra keys are dropped and missing columns become `NULL`. |
 

package/docs/reference/glob.md

@@ -0,0 +1,140 @@
+# Globs
+
+A glob is the string you write where a table name goes (`FROM './docs/*.md'`)
+or in a config `[[table]]`'s `glob`. dirsql reads it the way `bash` does with
+`globstar` on and `dotglob` off, and every place it does not is listed under
+[Divergences from bash](#divergences-from-bash).
+
+## Why bash
+
+Bash with `globstar` is the most popular glob behavior. Bash, zsh, node-glob
+and minimatch (npm, ESLint, VS Code, GitHub Actions) and Python's `glob` agree
+on one core: `*`, `?` and `[...]`, recursive `**`, `{a,b}` braces, `*` hiding
+dotfiles, and `**` not entering symlinked directories. Python has no braces
+and follows symlinks; bash breaks that tie. POSIX has no `**` or braces. So
+there is one standard nobody has to learn, the same string works in a
+[path-table](./path-tables.md) and in a [config](./config.md) `glob`, and each
+divergence is a written decision.
+
+## The fixture
+
+Every example below runs against this tree. A name ending in `/` is an empty
+directory, `a -> b` is a symlink, and `.gitignore` holds `*.log`.
+
+<!-- conformance-tree -->
+```text
+top.md
+a.md
+b.md
+c.md
+1.md
+2.md
+3.md
+4.md
+x.txt
+ignored.log
+{q}.md
+[a].md
+[z.md
+my file.md
+.env
+.git/
+.config/app.toml
+.config/.secret
+.config/sub/deep.md
+docs/guide.md
+docs/api.md
+docs/.draft.md
+docs/nested/deep.md
+docs/nested/.cache/x.md
+node_modules/pkg/index.js
+real/r.md
+linkdir -> real
+link.md -> top.md
+broken -> nowhere
+```
+
+## Examples
+
+Each row lists the files the pattern returns, sorted. Every row without a
+divergence was produced by `bash -O globstar -O nullglob` with `dotglob` off,
+run from the fixture's root, keeping only files. The `Divergence` column names
+the rule from [below](#divergences-from-bash) that makes a row differ from
+bash's raw output. `$ROOT` is the fixture's directory and `$BASE` its parent.
+
+A test runs every row against dirsql as a path-table and, with the leading
+`./` dropped, as a config `glob`, so this table cannot drift from the code.
+
+<!-- conformance-table -->
+| Pattern | Rows | Divergence |
+| --- | --- | --- |
+| `./*.md` | `1.md`, `2.md`, `3.md`, `4.md`, `[a].md`, `[z.md`, `a.md`, `b.md`, `c.md`, `link.md`, `my file.md`, `top.md`, `{q}.md` |  |
+| `./**/*.md` | `1.md`, `2.md`, `3.md`, `4.md`, `[a].md`, `[z.md`, `a.md`, `b.md`, `c.md`, `docs/api.md`, `docs/guide.md`, `docs/nested/deep.md`, `link.md`, `linkdir/r.md`, `my file.md`, `real/r.md`, `top.md`, `{q}.md` |  |
+| `./**` | `1.md`, `2.md`, `3.md`, `4.md`, `[a].md`, `[z.md`, `a.md`, `b.md`, `c.md`, `docs/api.md`, `docs/guide.md`, `docs/nested/deep.md`, `link.md`, `my file.md`, `real/r.md`, `top.md`, `x.txt`, `{q}.md` |  |
+| `./?.md` | `1.md`, `2.md`, `3.md`, `4.md`, `a.md`, `b.md`, `c.md` |  |
+| `./[ab].md` | `a.md`, `b.md` |  |
+| `./[!a].md` | `1.md`, `2.md`, `3.md`, `4.md`, `b.md`, `c.md` |  |
+| `./\[a\].md` | `[a].md` |  |
+| `./[z.md` | `[z.md` |  |
+| `./{a,b}.md` | `a.md`, `b.md` |  |
+| `./{q}.md` | `{q}.md` |  |
+| `./{a.md` | none |  |
+| `./{1..3}.md` | `1.md`, `2.md`, `3.md` |  |
+| `./my file.md` | `my file.md` |  |
+| `./.*` | `.env`, `.gitignore` |  |
+| `./**/.*` | `.env`, `.gitignore`, `docs/.draft.md` |  |
+| `./.env` | `.env` |  |
+| `./.config/**` | `.config/app.toml`, `.config/sub/deep.md` |  |
+| `./docs/.*` | `docs/.draft.md` |  |
+| `./link.md` | `link.md` |  |
+| `./linkdir/*` | `linkdir/r.md` |  |
+| `./*/r.md` | `linkdir/r.md`, `real/r.md` |  |
+| `./**/r.md` | `linkdir/r.md`, `real/r.md` |  |
+| `./real/**` | `real/r.md` |  |
+| `./docs` | `docs/api.md`, `docs/guide.md` | directory-name |
+| `./docs/` | `docs/api.md`, `docs/guide.md` | directory-name |
+| `./*/` | `docs/api.md`, `docs/guide.md`, `linkdir/r.md`, `real/r.md` | directory-name |
+| `./d*` | none | files-only |
+| `./*.log` | none | gitignore |
+| `./**/*.js` | none | node-modules |
+| `./node_modules/*/index.js` | `node_modules/pkg/index.js` |  |
+| `./docs/**/*.md` | `docs/api.md`, `docs/guide.md`, `docs/nested/deep.md` |  |
+| `./docs/*.md` | `docs/api.md`, `docs/guide.md` |  |
+| `$ROOT/docs/*.md` | `$ROOT/docs/api.md`, `$ROOT/docs/guide.md` | absolute |
+| `~/docs/*.md` | `$ROOT/docs/api.md`, `$ROOT/docs/guide.md` | absolute |
+| `../proj/docs/*.md` | `$BASE/proj/docs/api.md`, `$BASE/proj/docs/guide.md` | absolute |
+
+## Divergences from bash
+
+| Tag | Rule | Why |
+| --- | --- | --- |
+| `gitignore` | Inside a git repo, `.gitignore` files hide matching files and directories. `--no-ignore` turns it off. | A query over a repo should not drown in build output. |
+| `directory-name` | A pattern's last component that names a directory lists the files directly inside it, like `ls docs`. A trailing `/` is `*` appended. | A table is rows of files, and `ls` is the shell habit. |
+| `files-only` | A pattern that matches a directory but no file returns nothing. | Every row is a file. |
+| `node-modules` | A `node_modules` directory is skipped unless the pattern spells its name. | A zero-config `./**` should not walk dependencies. |
+| `absolute` | `/`, `~/` and `../` patterns report absolute `path` values, with `..` folded out textually. | The scanned root is derived from the pattern, so there is no relative base. |
+
+`.git` needs no rule of its own: the dotfile rule hides it.
+
+## Where the glob is anchored
+
+A path-table pattern is relative to the index root and starts with `./`. A config `[[table]] glob`
+is relative to the directory holding its config file, whatever directory you
+run `dirsql` from, and is written without the `./`: `./docs/*.md` in a path-table
+is `glob = "docs/*.md"` in a config. A config table whose glob matches no files prints
+`dirsql: table 'name': glob 'pattern' matched no files under <anchor>` to
+stderr; the exit code is unchanged. Path-tables never warn.
+
+## Edge cases
+
+- A `{`, `}` or `[` with no partner is a literal character.
+- A brace group with no comma and no `..` is literal (`{q}`); `{1..3}` and
+  `{a..c}` expand, as do zero-padded
+  `{01..10}` and stepped `{1..10..2}` ranges. Groups nest.
+- `\[` is a literal bracket.
+- A dot-named file or directory is listed only where a component spells the
+  dot at that depth: `./**/.*` finds `docs/.draft.md` but does not enter
+  `.config/`.
+- A symlinked file is a file. A symlinked directory is entered by any component
+  except `**`.
+- A broken link lists nothing.

package/docs/reference/path-tables.md

@@ -52,16 +52,8 @@ depth, as in the shell. A trailing `/` is `*` appended, so `'./*/'` is
 | `'./notes/today.md'` | exactly that one file — one file is one row |
 
 A path containing `*`, `?`, `[` or `{` is a glob and is used exactly as
-written: `*` matches within a single directory, `**` crosses directories.
-
-Braces expand as bash expands them. A group holding a comma is an
-alternation: `'./docs/{a,b}.md'` is `docs/a.md` and `docs/b.md`, and groups
-nest. A group holding a `..` range counts: `'./log/{1..3}.txt'`,
-`'./{a..c}.md'`, `'./{01..10}.md'` (zero-padded) and `'./{1..10..2}.md'`
-(every second value). Any other brace is literal text, so `'./br/{q}.md'`
-names the file `br/{q}.md`, and `\{` is always a literal brace. A `{`, `}`
-or `[` with no partner is literal too, in a path-table and in a config
-`[[table]] glob`.
+written. The [glob page](./glob.md) has the syntax, examples and every
+divergence from bash, including braces and unbalanced brackets.
 
 The scan starts at the last directory named outright before the first glob
 component, and descends only as deep as the pattern can match --

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dirsql",
-  "version": "0.4.98",
+  "version": "0.4.100",
   "description": "Ephemeral SQL index over a local directory",
   "license": "MIT",
   "repository": "https://github.com/thekevinscott/dirsql",
@@ -221,10 +221,10 @@
     ]
   },
   "optionalDependencies": {
-    "@dirsql/lib-linux-x64-gnu": "0.4.98",
-    "@dirsql/lib-linux-arm64-gnu": "0.4.98",
-    "@dirsql/lib-darwin-x64": "0.4.98",
-    "@dirsql/lib-darwin-arm64": "0.4.98",
-    "@dirsql/lib-win32-x64-msvc": "0.4.98"
+    "@dirsql/lib-linux-x64-gnu": "0.4.100",
+    "@dirsql/lib-linux-arm64-gnu": "0.4.100",
+    "@dirsql/lib-darwin-x64": "0.4.100",
+    "@dirsql/lib-darwin-arm64": "0.4.100",
+    "@dirsql/lib-win32-x64-msvc": "0.4.100"
   }
 }