@suss/adapter-ruby 0.30.0 → 0.31.1

package/README.md

@@ -29,6 +29,10 @@ npx suss check --dir summaries/
 
 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.
+
 ## Where it fits
 
 It depends on `@suss/extractor`, `@suss/behavioral-ir`, `@suss/datalog` and `web-tree-sitter`. The `rails` and `graphql-ruby` packs consume its `RubyPack` contract. Nothing here knows what any particular library's classes or base classes are called; a pack says that.