Wappler Version : v6 beta 8
Server Model: PHP
What do you think should happen?
As happens in the stable release, an empty flow should be allowed to be called and should not create a console error, for example:
<script is="dmx-flow" id="flow_save_last_edited" type="text/dmx-flow"></script>
flow_save_last_edited.run()
What actually happens?
In beta 8, this situation causes a console error:
I think it is actually a good thing it throws the error, when would you want to run a flow that hasn’t any flow defined.
When it is a shell for something you will add in a future release…
… any chance the error could be removed for compatibility?
I happen take quite a few of these and I don’t want to have to take them all out and then add them all back in later!
I think having feedback is good, it will remind you that it still needs to be implemented. Throwing an error is probably not correct, but showing a warning in the console instead should be ok.
Fixed in Wappler 6 beta 10