Suggestion: Request History for Library Functions

Abdulrahman Hariri

Hello,

I was wondering if it would be possible to have a "Request history" for the standalone functions, similar to the ones within the actual endpoints? This would make it much easier to debug issues especially when chaining functions (i.e. endpoint going to a function that goes into more functions).

Thanks!

arturosanz

@Abdulrahman Hariri

🤗 Want to submit a feature request? Click here.

Ray Deck

YOu can address this somewhat by making an event log that populates at the top of each run of a function. I recently made a video fo the general technique:

https://youtu.be/_8wAnQagI2Y?si=5AAuoIbVqK6ULe1t

Abdulrahman Hariri

@Ray Deck That's an excellent idea! While this is definitely useful, I was hoping we could do this without having to store logs 😀. Maybe if there was a way to trigger this function when errors happen somehow.

Ray Deck

You could put the function call in the catch of a try…catch in that case.

Some of what you are looking for is in services like bugsnag or sentry, that have the job of wrapping code to trap and report errors. But Xano (and most other NCLC services) doesn't have code to trap, so we implement these workarounds.

Abdulrahman Hariri

@Ray Deck Nice, will try the try/catch, never used it so far 😀 Thanks!