Skip to content

Commit d97d2e3

Browse files
committed
docs(skills): pay the formula skill's token ceiling back after the sparse-action paragraph landed
The merged file read 6086 tokens against the 5997 ceiling. Paid by deletion in the same file: the flow-condition callout drops its restated "prefer record.x" sentence and the two-door clause now says only that the runtime publish gate resolves no bare name; the "Null + string throws" section restated pattern 1 (always coalesce; CEL throws on null + string); the ABORTS paragraph restated pattern 3's compile sentence and the previous-table's insert-leg remedy. Reads 5956 of 5997 after. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WGufzfSZ55f7xwAfpfkPgY
1 parent 3ddf537 commit d97d2e3

1 file changed

Lines changed: 7 additions & 17 deletions

File tree

‎skills/objectstack-formula/SKILL.md‎

Lines changed: 7 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -140,12 +140,6 @@ has(record.amount) && record.amount != null && record.amount > 1000
140140
has(record.viewer) && has(record.viewer.can_approve) && record.viewer.can_approve == true
141141
```
142142

143-
### Null + string throws
144-
145-
CEL has no implicit `null` coercion. `null + 'foo'` throws
146-
`no such overload: dyn<null> + string`. Wrap every nullable string operand
147-
in `coalesce(..., '')`.
148-
149143
---
150144

151145
## ObjectStack CEL standard library
@@ -342,9 +336,7 @@ a typo'd key (`record.stauts`), a retired field, or a comparison CEL has no
342336
overload for — does **not** degrade to "the hook did not fire": it **fails the
343337
write**, with an error naming the hook and the key — `before*` and `after*`
344338
alike, with no `onError` escape (`onError` governs a handler that throws, and
345-
the condition is evaluated before any handler runs). A condition that does not
346-
even **compile** aborts the same way. So on an insert event read `previous`
347-
only against `null`, and put a column read off it behind `previous != null &&`.
339+
the condition is evaluated before any handler runs).
348340

349341
**A transition condition needs no special handling for bulk writes.**
350342
Write it once, on a `before*` or an `after*` event, and it means the same thing
@@ -407,14 +399,12 @@ When migrating Salesforce-flavor metadata, apply these rules in order:
407399
> ⚠️ **Flow conditions are the exception to row 1.** The engine spreads the
408400
> trigger record's fields, nulls included, to top level wherever no flow variable
409401
> or node id holds the name, so in a start, edge or `decision` condition a bare
410-
> `budget` IS `record.budget`: `os validate` judges either spelling (bare
411-
> names only while every node's bindings are declared), a guard on one spelling
412-
> guards both, and what the start condition proves non-null is presumed at every
413-
> edge and branch. Spell that start guard `record.budget != null`: the runtime
414-
> publish gate judges the written flow alone, proves nothing from a bare
415-
> `budget != null`, and refuses the edge `os validate` passed. An unguarded null
416-
> fails the **run** at that condition; the write that fired it still lands.
417-
> `record.x` is the only spelling valid on every other surface — prefer it.
402+
> `budget` IS `record.budget`: `os validate` judges either spelling (bare names
403+
> only while every node's bindings are declared) and a guard on one guards both.
404+
> What the start condition proves non-null is presumed at every edge and branch;
405+
> spell that guard `record.budget != null` — the runtime publish gate judges the
406+
> written flow alone and resolves no bare name. An unguarded null fails the
407+
> **run** at that condition; the write that fired it still lands.
418408
419409
---
420410

0 commit comments

Comments
 (0)