Skip to content

Conversation

bjacobgordon
Copy link
Collaborator

  • the built-in JS errors considered "non-actionable" hold enough context on their own
  • nesting them ends with in new NonActionableError instances just needlessly obfuscates the reason for failure

@bjacobgordon bjacobgordon self-assigned this May 30, 2025
@bjacobgordon bjacobgordon force-pushed the fix-library-avoids-nesting-built-in-non-actionable-errors-in-Attempt-utility branch from 91dcfb3 to aea3428 Compare May 30, 2025 13:09
@bjacobgordon bjacobgordon changed the title fix(library) avoids nesting built-in non-actionable errors in Attempt utility fix(library): avoids nesting built-in non-actionable errors in Attempt utility May 30, 2025
@github-actions github-actions bot added the fix label May 30, 2025
@bjacobgordon bjacobgordon merged commit 4f792ed into nod-ai:integration May 30, 2025
2 of 3 checks passed
@bjacobgordon bjacobgordon deleted the fix-library-avoids-nesting-built-in-non-actionable-errors-in-Attempt-utility branch May 30, 2025 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

prefeature: replace default error propagation with linter-enforceable type-safe variety
1 participant