Klemen Tusar

> Let's have an open discussion about the best way to handle this generically and then see if it needs to be implemented. Agreed. There is no simple answer here.

It just dawned on me that this could be mitigated with `dart fix` as described in [Data-driven Fixes](https://github.com/flutter/flutter/blob/master/docs/contributing/Data-driven-Fixes.md). What do you guys think?

Or you define that via an environment variable or file that you pass at compilation of the flavour. Based on that variable you either include Alice or don't. To achieve...

**`WeakReference`/`Finalizer` are low-level primitives, NOT a drop-in replacement for an `Expando`-backed weak-key map.** A `WeakReference` gives you a single weak pointer whose .target may become `null` after GC; it doesn’t...

> > > Yes, the output result of using flutter doctor -v is indeed JDK 21. However, my local configuration is jdk17. I don't know why flutter will default to...

@DavidCorrado you could use a library like [qs-kotlin](https://github.com/techouse/qs-kotlin) to pre-serialize your data. For example, you could take your `Map` (with ints, strings, etc.) and let qs-kotlin turn it into a...

Still not fixed in 5.4.27 :(

@EArminjon hmm, not sure. At the moment of writing [open_filex](https://pub.dev/packages/open_filex) looks more up to date than [open_file](https://pub.dev/packages/open_file).

> As far as I can see, there is always only a single instance that is being created since the field was always marked `static final`. Fair point.

Well, I can add more docs, but I'm reluctant to remove `@protected` from the relations as it exposes internal mechanics to the user.