#Flutter tip: avoid calling setState() in a long build method or all the child widgets in it will rebuild!The best solution would be to destructure your build method into multiple small widgets. But if you can’t do that for some case, use the #ValueNotifier widget
I may have to try this. I've been using optional arguments with defaults for this instead. For more complex objects this can be more expressive. I've used it for other components (data, service, etc.) but never Widgets.
🧐 Flutter #refactoring tip
Make your widgets more readable using factories
Did you know that #Flutter is good for your #allergies? 😏 Specially if you're allergic to #StatefulWidget and would rather have #StatelessWidget 🤠 In many cases you can use #ValueNotifier and #ValueListenableBuilder to avoid making your widgets stateful!
