Determine which provider was modified during build

[dickermoshe]

We all have seen this error:

But I've got lots of widgets and tons of providers, is there a way to get a better error message than this?

[rrousselGit]

The error is from Flutter.

The StackTrace should point you to the problematic code

[dickermoshe]

Good point, I see that in the debugger:

But it shouldn't it also be shown in the error message?
When running an app in debug mode, you only see the message, the stacktrace is not shown in the terminal until you press "Continue"

It would nice if the message could extract this from the err object.

@rrousselGit Thank you so much for this package, it's a gem!

[rrousselGit]

The stacktrace should be visible in vscode when paused at an error. It's in the debugging panel.

As for the error's toString, I'm not responsible for this error, so I have no control over it. I'm not sure why they would or wouldn't show the ErrorDescription

[dickermoshe]

Incorrect, the error being shown is from riverpod.
It would be nice if this err was put directly in the message:

[dickermoshe]

riverpod/packages/flutter_riverpod/lib/src/framework.dart

Lines 348 to 377 in 9e62837

	} catch (err) {
	throw FlutterError.fromParts([
	ErrorSummary(
	'Tried to modify a provider while the widget tree was building.',
	),
	ErrorDescription(
	'''
	If you are encountering this error, chances are you tried to modify a provider
	in a widget life-cycle, such as but not limited to:
	- build
	- initState
	- dispose
	- didUpdateWidget
	- didChangeDependencies
	Modifying a provider inside those life-cycles is not allowed, as it could
	lead to an inconsistent UI state. For example, two widgets could listen to the
	same provider, but incorrectly receive different states.
	To fix this problem, you have one of two solutions:
	- (preferred) Move the logic for modifying your provider outside of a widget
	life-cycle. For example, maybe you could update your provider inside a button's
	onPressed instead.
	- Delay your modification, such as by encapsulating the modification
	in a `Future(() {...})`.
	This will perform your update after the widget tree is done building.
	''',
	),

[dickermoshe]

I guess the flutter error message ain't great to begin with.