Luca Venir

@Fbartoli read the above comments to make it work. It's a silly npm error.

This is completed because... there's a way to avoid encoding query parameters without the above workaround? The above workaround *doesn't* work for me. The parameters still gets encoded. Aka I...

Hi @russellwheatley! Thank you!! This is very helpful. @adar2378 sorry I didn't reply, I hadn't the time to verify your suggestion. Thank you for being active, kind interest and for...

This topic should be addressed in the documentation rework. Maybe inside the "notable Cookbooks examples" section. such guide in particular should be cross-referenced in the "migration from Provider" quickstart.

@tobiasbentin I know you didn't ask me, but please read the new documentation, it basically answers your question, but to put it shortly AVOID doing shenanigans with container before `ProviderScope`....

@rrousselGit one thing that imo is missing from the page is mentioning how using `ref.keepAlive` for some one-time-asynchronous singletons is key to avoiding `StateError`s when using `.requireValue` on eagerly initialized...

Naming should have been `both` for what is meant now, whereas it should be named `always` for the purpose of this issue

I personally like this, but this should deprecate `ShowValueIndicator.never` as it overlaps with the other dimension.

I just stumbled upon this. It was a bit of a paper cut, I didn't expect `field_rename` not to work for `JsonEnum` (indeed `build.yaml` configurations are documented as "global"). It...

I've seen the [pull request](https://github.com/flutter/packages/pull/2650) associated with this issue. That's phenomenal! I just wanted to ask: why is it introducing a new API for "stateful" shell navigation? Isn't that... "overcomplicating"...