Is there a workaround to avoid having to rename all our API calls and remove leading _underscores
What purpose does this serve @patrick
In programming it is very common to mark methods and properties as private by prefixing them with an underscore. This convention is also used in many routing implementations like in Next.js and Astro.
The actions are still accessible from other actions but not from a public Url. This was implemented since some actions you don't want to be accessible to the public, like actions run by a cronjob to cleanup the database or for sending emails. Since it was often requested to make an action private, we implemented it like this since it was a very common way to do so.
There is no workaround, you'll have to rename the actions or edit the routes.js file and comment that line out.
Ok, thanks.
Does the routes.js file get updated often?
Don't worry about it.
It's a case of brush up on regex and get it sorted.
Thanks all for your help
"The actions are still accessible from other actions but not from a public Url. This was implemented since some actions you don't want to be accessible to the public."
A hammer to crack a nut.
You provide library calls for just this purpose.
And security models.
Not a solution. An explanation
Did a Wappler update just break an existing website then? I thought it was sacred to not break existing websites!
Not that I'm affected, I just found it funny 
And then people are scared of updating Wappler... Maybe this change should've been communicated better
Why do you think that?
If for the underscore functionality- it is been there for quite a while, nothing new.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.