Add tests and CLAUDE.md

Author: dsherret

CLAUDE.md

@@ -0,0 +1,45 @@
+# dprint-plugin-sql
+
+Wrapper around [sqlformat-rs](https://github.com/shssoichiro/sqlformat-rs) for use as a dprint formatting plugin.
+
+## Commands
+
+- `cargo test` — run all tests
+- `cargo build --target wasm32-unknown-unknown --features wasm --release` — build the wasm plugin
+- `cd deployment/npm && node setup.js && npm test` — test the npm package (requires wasm build first)
+
+## Architecture
+
+- `src/format_text.rs` — core formatting logic, delegates to `sqlformat::format()`
+- `src/wasm_plugin.rs` — dprint wasm plugin interface (compiled only for wasm32 target with `wasm` feature)
+- `src/configuration/` — config types, resolution, and builder
+- `deployment/npm/` — npm package that ships `plugin.wasm`
+- `deployment/schema.json` — JSON schema for plugin configuration
+- `scripts/update.ts` — Deno script that checks crates.io for new sqlformat versions and auto-publishes
+- `scripts/generateReleaseNotes.ts` — generates changelog for GitHub releases
+
+## Adding a new config option
+
+When sqlformat-rs adds new options:
+
+1. Add the field to `Configuration` in `src/configuration/configuration.rs` (add enums with `generate_str_to_from!` if needed)
+2. Add resolution in `src/configuration/resolve_config.rs` using `get_value()`
+3. Add a builder method in `src/configuration/builder.rs` and update the `check_all_values_set` test
+4. Wire it through in `src/format_text.rs` when constructing `FormatOptions`
+5. Add the property to `deployment/schema.json`
+6. Add a spec test file in `tests/specs/Config/`
+
+## Test specs
+
+Spec files live in `tests/specs/` and use the dprint-development format:
+
+- `== message ==` starts a test case
+- `[expect]` separates input from expected output
+- `~~ key: value, key: value ~~` at the top of a file sets config for all specs in that file
+- Each config variation needs its own file since config is file-level
+
+## Releases
+
+- Manual: trigger the `release` workflow with patch/minor
+- Automatic: `check_updates` workflow runs daily, detects new sqlformat versions, and auto-publishes
+- On tag push: CI creates a GitHub release with `plugin.wasm`, and `publish_npm` publishes to npm

tests/specs/Basic/Basic_All.txt

@@ -1,22 +1,84 @@
-== should format basic ==
-SELECT *   FROM   dbo.Test    WHERE   test =   'asdf'
-GO
-
-
-
-update dbo.Test Set test=1
-GO
-
-[expect]
-SELECT
-  *
-FROM
-  dbo.Test
-WHERE
-  test = 'asdf'
-GO
-update
-  dbo.Test
-Set
-  test = 1
-GO
+== should format basic ==
+SELECT *   FROM   dbo.Test    WHERE   test =   'asdf'
+GO
+
+
+
+update dbo.Test Set test=1
+GO
+
+[expect]
+SELECT
+  *
+FROM
+  dbo.Test
+WHERE
+  test = 'asdf'
+GO
+update
+  dbo.Test
+Set
+  test = 1
+GO
+
+== should format subquery ==
+SELECT * FROM (SELECT id, name FROM users WHERE active = 1) AS t WHERE t.id > 10
+
+[expect]
+SELECT
+  *
+FROM
+  (
+    SELECT
+      id,
+      name
+    FROM
+      users
+    WHERE
+      active = 1
+  ) AS t
+WHERE
+  t.id > 10
+
+== should format insert ==
+INSERT INTO users (id, name, email) VALUES (1, 'test', 'test@example.com')
+
+[expect]
+INSERT INTO
+  users (id, name, email)
+VALUES
+  (1, 'test', 'test@example.com')
+
+== should format join ==
+SELECT u.name, o.total FROM users u INNER JOIN orders o ON u.id = o.user_id WHERE o.total > 100
+
+[expect]
+SELECT
+  u.name,
+  o.total
+FROM
+  users u
+  INNER JOIN orders o ON u.id = o.user_id
+WHERE
+  o.total > 100
+
+== should format create table ==
+CREATE TABLE users (id INT PRIMARY KEY, name VARCHAR(255) NOT NULL, email VARCHAR(255) UNIQUE)
+
+[expect]
+CREATE TABLE users (
+  id INT PRIMARY KEY,
+  name VARCHAR(255) NOT NULL,
+  email VARCHAR(255) UNIQUE
+)
+
+== should format multiple queries ==
+SELECT 1; SELECT 2; SELECT 3
+
+[expect]
+SELECT
+  1;
+SELECT
+  2;
+SELECT
+  3

tests/specs/Config/Casing.txt

@@ -0,0 +1,10 @@
+== should preserve casing by default ==
+SELECT * FROM users WHERE id = 1
+
+[expect]
+SELECT
+  *
+FROM
+  users
+WHERE
+  id = 1

tests/specs/Config/CasingLower.txt

@@ -0,0 +1,11 @@
+~~ casing: lower ~~
+== should lowercase with casing lower ==
+SELECT * FROM users WHERE id = 1
+
+[expect]
+select
+  *
+from
+  users
+where
+  id = 1

tests/specs/Config/CasingUpper.txt

@@ -0,0 +1,11 @@
+~~ casing: upper ~~
+== should uppercase with casing upper ==
+select * from users where id = 1
+
+[expect]
+SELECT
+  *
+FROM
+  users
+WHERE
+  id = 1

tests/specs/Config/Indent.txt

@@ -0,0 +1,11 @@
+~~ useTabs: true ~~
+== should use tabs ==
+SELECT * FROM users WHERE id = 1
+
+[expect]
+SELECT
+	*
+FROM
+	users
+WHERE
+	id = 1

tests/specs/Config/IndentWidth.txt

@@ -0,0 +1,11 @@
+~~ indentWidth: 4 ~~
+== should use 4 space indent ==
+SELECT * FROM users WHERE id = 1
+
+[expect]
+SELECT
+    *
+FROM
+    users
+WHERE
+    id = 1

tests/specs/Config/JoinsAsTopLevel.txt

@@ -0,0 +1,14 @@
+~~ joinsAsTopLevel: true ~~
+== should treat joins as top level ==
+SELECT u.name, o.total FROM users u INNER JOIN orders o ON u.id = o.user_id LEFT JOIN payments p ON o.id = p.order_id
+
+[expect]
+SELECT
+  u.name,
+  o.total
+FROM
+  users u
+INNER JOIN
+  orders o ON u.id = o.user_id
+LEFT JOIN
+  payments p ON o.id = p.order_id

tests/specs/Config/LinesBetweenQueries.txt

@@ -0,0 +1,10 @@
+~~ linesBetweenQueries: 2 ~~
+== should use 2 lines between queries ==
+SELECT 1; SELECT 2
+
+[expect]
+SELECT
+  1;
+
+SELECT
+  2

tests/specs/Config/UppercaseLegacy.txt

@@ -0,0 +1,11 @@
+~~ uppercase: true ~~
+== should support legacy uppercase boolean ==
+select * from users where id = 1
+
+[expect]
+SELECT
+  *
+FROM
+  users
+WHERE
+  id = 1