-
Branching/merging workflow with a team
Our team has been using Xano alongside WeWeb, and we're starting to explore the branching experience. I feel like it could be improved. In WeWeb, if you want to connect your staging environment with a non-live Xano branch, you have to hard code the name of that branch. In our case, we'd like to use 'staging'. Therefore in…
-
Xano quality of life suggestions
Hi, I have been in extensive development time for some time now (moving away from bubble following their disastrous pricing changes), but there's a few things I'd love to see as improvements in Xano. I don't want to clutter the forum with multiple requests, so thought I'd summarise here with my "wishlist". Already I'm…
-
Variable auto fill : Please, remove the id switching automatically to auth:id.
I understand that the auto fill was an amazing quality of life change to prevent variables being entered as texts. However, there should be list of exceptions, like the word id. So many times I encountered the ACCES_DENIED error because I filled the field value as auth:id instead of id. id should be id input as text first…
-
Metadata API: task history?
The metadata API is a game-changer. We plan to leverage it to create enhanced API error and performance monitoring via the "request history" endpoints. However, I wanted to clarify - is there currently no method to monitor task run history? Ideally, we'd be able to access a similar API for this purpose. Thank you, Wes
-
Annoying & Disruptive Changes to Xano Debugger
Hi Xano team & community, I noticed a recent update to Xano's debugger has removed critical functionality and is counter-intuitive. I have been developing with Xano for over a year now and this is a crucial step for optimising calls. The debugger used to give a break down of time on each step but now it just groups…
-
Sprintf arguments
It would be great if we could rearrange sprintf arguments in the editor, especially when we are building longer concatenated strings and need to insert an argument toward the beginning of the list. I have had to undo and redo many arguments because of this.
-
1,000 entry limit in stack trace
Is the 1,000 entry limit in the stack trace new? I don't seem to remember hitting it nearly as often as I'm seeing now. Is there any way around this via plans (current instance is launch), or do I need to go back and further break up my functions for debugging?