Logging inconsistencies with Flutter about flutter HOT 5 OPEN

Tagging @matanlurey since he told me to do so

from flutter.

Using debugPrint or surrounding print with if (kIsDebug) isn't even the same behavior though.

Problems:

• debugPrint has nothing to do with other uses of the prefix debug in the framework, which imply debug mode.
• The default print could be fixed in the Flutter embedder (read: not require zones) to make debugPrint unnecessary
• It's not clear to users when to use dart:developer#log, which is also part of the API that ships with Flutter

from flutter.

Appreciate you filing this.

I don't have the authority to make such a change, but here is what I would do if I did:

• Override print in the Flutter embedder to work the way debugPrint does today
• Deprecate debugPrint (for the time being, have it just forward to print)

That would bring us down to 2 ways to do things - one that always works in every mode and device - and one for debug only. I expect folks would likely write higher-level utilities on top, but at least the core functionality in dart:* would work in a reasonable manner.

@darshankawar I don't think this is team-engine (yet), it's true the change would need to happen in the engine, but the framework team would need to sign off on the changes (and, in my proposal above, agree to deprecate debugPrint).

from flutter.

From the framework's point of view you should be using debugPrint (this is also enforced with the avoid_print lint, which is part of the recommended lint set for flutter). By convention (like anything starting with debug*) it should only be called from a debug context (i.e. within an assert or guarded by if (kIsDebug)), see also its documentation. It solves the throttling problem on some platforms and makes it really easy to intercept logs in tests (without requiring the use of error-prone zones).

I guess, it is not clear to me what problem this issue is describing that needs to be solved?

from flutter.

debugPrint. The name suggests that it will only log to the console in debug mode, but nope; it’s nothing to do with whether you’re in debug of release mode. Massive foot gun for people new to Dart. I suspect a lot of Dart apps are leaking all sorts of info because of this…

from flutter.