-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
enhancementNew feature or requestNew feature or requestfeedback:wild-lycheeFeedback from Wild Lychee buildFeedback from Wild Lychee build
Description
Problem
Deployed a function with a runtime error (used db.sql() with $1 params before that feature existed). Deploy succeeded — the error only surfaced when the function was invoked. No feedback until a user hit the broken code path.
Suggested Solution
Add basic validation during run402 functions deploy:
node --check <file>catches syntax errors- Optionally, a
--validateflag that does a dry-run import
Even catching obvious syntax errors would save significant debugging time.
Context
Spent 3 deploy cycles debugging a function that could have been caught at deploy time.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestfeedback:wild-lycheeFeedback from Wild Lychee buildFeedback from Wild Lychee build