I know you are hard at work but I thought I should reach out and submit a request that I think every Wappler would want. The ability to simply copy and paste server actions would save sooo much time! I know you can bring up the json file in code view then copy the whole thing and paste it into another action and then edit it as needed but this is still time consuming.
No, that's not what I was referring to. I mean, lets say you have an action in your server action that is a complex API call, or a datbase search, etc, having the ability to right click that particular action, and copy then navigate to another sever action, and paste. So not the actual server action, but the actions inside it
I still don't understand what the criteria are for defining when something requested by the community in a vote is included or not in Wappler.
I had already voted here:
I understand that there is a roadmap to be followed, and that the team works hard, and I saw that some requests are met. But I think there could be more transparency in these requests.
For example: when a certain number of votes is reached, the team could at least express itself and include a tag in the vote such as:
"We won't do it", "Impossible to do it", "We are thinking about it", "planned for Wappler V12", that is, at the very least, keep the community informed.
Otherwise, we will end up voting on something meaningless, something that in some cases the team doesn't even say anything about. "Switch case" has been around for over 6 years. Maybe it will come out someday, let's not lose hope.
Well, just one suggestion to improve communication. The answer to the request is important even if it is a "no".
A lot of factors go into deciding when, or if, a feature is added to Wappler.
Sometimes it's just a matter of technical limitations—some things are harder to do than they seem, and that can delay or even prevent them from being added.
So something that sounds to you like "just doing this and that" requires a lot of work under hood.
Also, our roadmap is not fixed—it’s a living document that changes over time as priorities shift. What may not be a focus today could very well become a priority later as user needs evolve in a certain direction.
Community votes do help a lot. The more votes a feature gets, the more attention it gets from the team. But even with many votes, it doesn’t always mean it’ll be added right away.
It's not about "just doing this and that", I'm talking about communication. It's not about being obligated to do something, it's about communicating.
If what I said is a joke to you, I apologize for wanting to collaborate with the community. I think we should respect each other's opinions and the difficulties that each person has in the ecosystem. I'm always happy when I learn something new.
No one is treating it as a joke @Nilton_Felicio. The Wappler community is probably the most amicable and tolerant place within the space. We do like to nudge on each-other now and again but nothing is ever personal, and feedback is always much appreciated by all, Team and Members alike. Like Teodor has explained not everything can be incorporated immediately and some things take a great deal of thought and consideration, which takes time when there are so many other things going on in the background. But then once they are implemented we are all very appreciative that the thoughts and concerns of the Users were taken in to consideration as the outcome is usually very positive.
Copy and paste server action steps is now possible in Wappler 7 beta 6. You can copy and paste single or multiple steps between different server actions by simply using ctrl+c/cmd+c and ctrl+v/cmd+v shortcut keys.