@suss/adapter-ruby 0.32.0 → 0.33.0

package/README.md

@@ -26,12 +26,13 @@ npx suss check --dir summaries/
 - Rails controller actions, bound to the method and path `config/routes.rb` gives each one, with every status an action can respond with and the `before_action` filters that run in front of it.
 - graphql-ruby's class-based field DSL, including `mutation:` and `resolver:` wiring, and the method behind a field wherever it is defined in the class's ancestry.
 - ActiveRecord calls, what a file reads from the environment, and what a body calls out to, as facts the checker's rules run over.
+- SQL a project wrote itself and handed to a database client, parsed by `@suss/sql` into the tables it touches.
 
 How each of those is decided, and where it stops: [how the Ruby adapter reads a project](./DESIGN.md).
 
 ## Reading a value
 
-Nothing outside the facility reads a node's text to find out what a value is. `values/evaluator.ts` is the evaluator: `evaluatedValue` runs the statements ahead of an expression and says what it comes to, and `stringValueOf` gives the string when it settles to one, so a path built by interpolation or out of a constant reads the same as one written out. `facts/resolve.ts` says where a name came from, with `writtenValueOf` and `resolvedFunctions`, and the literal readers in `ast.ts` (`stringLiteralValue`, `symbolValue`, `booleanLiteralValue`) are for the places a literal really is written out. When one of them cannot read a spelling, the case goes into the evaluator's lowering or the resolution rules; `npm run check:readers` at the repo root fails on a reader written beside a call site instead. [`docs/internal/style.md#reading-a-value`](../../../docs/internal/style.md#reading-a-value) has the rule.
+Nothing outside the facility reads a node's text to find out what a value is. `values/evaluator.ts` is the evaluator: `evaluatedValue` runs the statements ahead of an expression and says what it comes to, and `stringValueOf` gives the string when it settles to one, so a path built by interpolation or out of a constant reads the same as one written out. `facts/resolve.ts` says where a name came from, with `writtenValueOf` and `resolvedFunctions`, and the literal readers in `ast.ts` (`stringLiteralValue`, `symbolValue`, `booleanLiteralValue`) are for the places a literal really is written out. When one of them cannot read a spelling, the case goes into the evaluator's lowering or the resolution rules; `npm run check:readers` at the repo root fails on a reader written beside a call site instead. [`design/docs-internal/style.md#reading-a-value`](../../../design/docs-internal/style.md#reading-a-value) has the rule.
 
 ## Where it fits
 
@@ -41,9 +42,9 @@ It depends on `@suss/extractor`, `@suss/behavioral-ir`, `@suss/datalog` and `web
 
 ## More
 
-- [Documentation](https://nimbuscloud-ai.github.io/suss/)
-- [Python and Ruby](https://nimbuscloud-ai.github.io/suss/guides/python-and-ruby)
-- [Every pack suss ships](https://nimbuscloud-ai.github.io/suss/reference/packages)
+- [Documentation](https://suss.sh/)
+- [Python and Ruby](https://suss.sh/guides/python-and-ruby)
+- [Every pack suss ships](https://suss.sh/packs/catalog)
 - [Source and issues](https://github.com/nimbuscloud-ai/suss)
 
 ![coverage](../../../.github/badges/coverage-ruby.svg)