HF-131 (7/7): documentation - #1767
marcin-kordas-hoc wants to merge 11 commits into
Conversation
ErrorType has ten members; this guide's error table only listed nine. Add the missing #SPILL! row, matching the existing table's style, plus a short note that HyperFormula does not turn a message into a longer plain-language explanation itself — an application layer wanting that should build it on top of the type/message the engine already provides. Docs-only, no CHANGELOG entry per this repo's DoD. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Task linked: HF-131 Verbose and actionable formula error messages |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9dbfe89. Configure here.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
hyperformula-docs | 67cd26e | Commit Preview URL Branch Preview URL |
Sep 15 2026, 08:03 AM |
Performance comparison of head (67cd26e) vs base (1879bbb) |
The page listed the error types but never mentioned originFunction, argumentIndex or hasMessage, so the only description of them was in the API reference. Also drops one tag: the page carried 11 against the guide's cap of 10, and 'division by zero' is the one tag that is a phrase rather than an error code, already covered by '#DIV/0!'. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## fix/hf-131-issue-444-addresses #1767 +/- ##
===============================================================
Coverage 97.45% 97.45%
===============================================================
Files 195 195
Lines 15868 15868
Branches 3500 3500
===============================================================
Hits 15464 15464
Misses 396 396
Partials 8 8 🚀 New features to boost your workflow:
|
Tobiadefami
left a comment
There was a problem hiding this comment.
Could we add { licenseKey: 'gpl-v3' } to the example’s buildFromArray() call? Without it, all three formulas return #LIC! instead of the documented results.

What and why
Stacked on #1766, the last in this stack. Documentation only.
#SPILL!row todocs/guide/types-of-errors.md(the type existed and wasproducible before this stack, just undocumented) and a new "Error messages and explanations"
section explaining what
messagedoes and doesn't do: it states the specific cause within anerror's type, but HyperFormula does not turn it into a longer plain-language explanation or call
out to an LLM to generate one — an application wanting to rephrase for end users should do so at
the application layer, using
type/messageas input.originFunction,argumentIndexand
hasMessage, with an example checked against the engine. Thecustom-functions.mdparagraphon
hasMessagelives in HF-131 (3/7): a consumer can tell 'no message' from 'empty message' #1763, not here.DOCS_CONTENT_GUIDE.md;division by zerois the only tag that is a phrase rather than an error code, and#DIV/0!already answers that query.
No
src/changes in this PR.Verified
npm run docs:build— clean, both new docs pieces present in rendered outputpre-existing branch-pinning mismatch as the rest of this stack (unaffected by a docs-only change,
included for completeness since it's the tip of the stack)
Stack
7 of 7 — stacked on #1766. Last PR in the HF-131 stack: #1761 → #1762 → #1763 → #1764 → #1765 →
#1766 → this one.
🤖 Generated with Claude Code
Note
Low Risk
Docs-only changes with no runtime or API behavior impact.
Overview
Documentation-only update to
types-of-errors.mdfor the HF-131 stack (nosrc/changes).The error reference table now includes
#SPILL!(array result has nowhere to spill), and frontmatter tags swapdivision by zerofor#SPILL!so the page stays within the 10-tag cap while keeping error-code tags consistent.Two new sections explain how apps should use
DetailedCellError:messagegives the specific cause within an error type but is not expanded or LLM-generated by HyperFormula (rephrasing belongs in the app layer), andoriginFunction,argumentIndex, andaddresshelp trace which function, argument, or mechanism produced the error, with a short JavaScript example.Reviewed by Cursor Bugbot for commit 67cd26e. Bugbot is set up for automated code reviews on this repo. Configure here.