Mateus Felipe C. C. Pinto
                                            Mateus Felipe C. C. Pinto
                                        
                                    I'm having the same problem as @aaronbieber, although it passes more than 2 years.
@feinstein I'm eager to see your PR!
Got it today. Basically, `State` and `ChangeNotifier` can't coexist in current Flutter because calling `super.dispose()` will call the `ChangeNotifier`s one. There are some workarounds, as the one proposed by @Levi-Lesches,...
Maybe the `aliases` approach would be better, as we should have a "canonical" reference to use in `toJson`. While `fromJson` could map from many different values to a single value,...
Yes, I'm surprised this is not the default behavior. We have some `JSON` objects that we have to parse in which we receive date fields as `millisecondsSinceEpoch`. I can't to:...
This would be a nice addition. Currently, we can implement it by manually marking the `sealed` class subtypes with `@JsonSerializable`, but if we want to have a `fromJson` in the...
> That doesn't apply to operators, because we don't have operator tear-offs anyway. (Well, _yet_!) @lrhn Is there any issue tracking this? I didn't find anything except for #691, which...
Could you please provide what use-cases you expect to cover to these? I can't really see the value of adding nameless classes.
@eernstg It seems that this new proposal doesn't have the possibility to `show` or `hide` members of the original type. Or am I missing something?
Although I recon the problem may exist, I think the suggestion is actually very counter-intuitive.