It's been a while since last
#Flutterflowtip
Today back to (debugging) basics:
Debug like a pro.
Use browser console π
You're testing your app, and some value isn't working as expected?
You probably jump off to editor, to create *text* widget to test this value.
While it's correct approach, it takes your previous space in app. Also, it can mess up your page design.
Instead, it's better to use tools created just for this - debugging tools.
To be more specific, it's console logs.
You can trigger logs using custom action.
Custom action for this is as simple as it can be - just one line.
Just add string argument to action, and write / ask Code Copilot to print this argument.
That's all it takes to write this custom action!
Now you can reuse it across your app as custom action, without messing up with your existing structure.
But what if you want to print a list?
Same method!
Just change parameters to list of string, and ask Copilot to print list to console.
To test it, on the web test/run mode open debug logs. Instructions are described here:
docs.flutterflow.io/troublesβ¦
#Flutterflow still doesn't offer so much options for debugging. With local run, we got
#Flutter devtools, but these can be daunting for regular user.
Hopefully FF team will introduce some debugging tools soon. But until that, console logging works like a charm!
Do you use this method?
Maybe you use some other way to debug things?
Share it in the comments!
#Flutterflow #Tip #NoCode #Lowcode