@remi_rousselet I wrote gen_expects and find it super helpful. It writes widget tests tho, not golden tests. What would an auto gen golden tests package look like? https://t.co/ESAJ7wRcFv
@b_plab98 1. I don't use app names or companies names in code because they often change. I used "Common" myself.
2. Wrapping something to stabilize it's API sounds nuts to me. Defensive coding like this rarely pays returns. I have a big common library but it's because of custom widgets.
@ASalvadorini Yeah. I get that. But have you ever seen the nightmare bugs mutable UI State can cause? I'm not saying they're not common. I just have never seen them.
@CFDevelop I suspect that in a lot of cases it's because the developer doesn't know much about the area that they need the package for, so don't know what to look for. So they go with the most popular. I know I've been guilty of this in the past.
@remi_rousselet One of the traps I've seen lately is the mistake that less code means cleaner code. Sometimes that's true but sometimes it means tighter coupling.
@kevmoo Agreed. I wrote my gen_keys package with it. Though I did find the documentation lacking for first time users. Probably because I'm spoiled by the great docs in Flutter