Repository navigation
Default handleError doesn't say which remote function failed schema validation #17418
Description
Describe the problem
A schema validation failure in a remote function logs the following by default:
Remote function schema validation failed: [ { message: 'Invalid type: Expected string but received undefined', ... } ]
The log doesn't say which remote function failed, so in an app with many queries it's hard to trace.
Writing your own handleError is the usual way around this, but it would be nice to have it dealt with by default.
Describe the proposed solution
Include the remote function name in log messages, so the default is enough to find the failing function.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response
Activity
Aman13sh commentedon Oct 13, 2026
I’d like to work on this,
teemingc commentedon Oct 13, 2026
Ideally, we'd locate the file and line the remote function was called, the file its declared in, the name of the remote function, etc. while stripping internals
Aman13sh commentedon Oct 13, 2026
Thanks! I’ll start with the remote function’s name and the file it’s declared in, since that looks available where validation happens. I’ll then look into whether the call-site file and line can be surfaced, and if that needs a bigger change I’ll check back here first. Does that sound good?
Aman13sh commentedon Oct 20, 2026
Hi @teemingc , I've opened #17495 covering the function name and the file it's declared in. Both are passed to
handleErrorasremote: { name, file }and included in the default log, e.g.Remote function getUser (src/routes/users.remote.js) schema validation failed: ....Before I look at the call site, a few questions so I don't go in the wrong direction:
remoteon the publichandleErrorinput okay, or should it stay internal to the default logger?Happy to add the call site to this PR or as a follow-up, whichever you prefer.