Why is default BAML_LOG behaviour info rather than warn?

[prrao87]

Thinking from a new user's perspective and flow here. When I start working with BAML and get my functions tested in the Playground, all's well. But when I then move my logic to my application, say in Python code, the BAML_LOG info is shoved in my face every time I run my Python code. It's far too easy for a new user to forget to run export BAML_LOG=WARN, or not even know that such an env variable exists in the first place.

Here's my logic for why a default behaviour of warn makes sense.

• The user begins their workflow in the BAML playground - prompts already work and are tested before a line of client code is written
• If we know that the prompts worked, it makes more sense to display the info log as opt-in only, because at this point, the user expects that their client application code returns the expected result
• It's trivial for users to pipe the logs to a database or text files after opting into the info level

IMO, the current flow is adding an unnecessary additional step each time application code is executed in a new BAML project for the first time. In many cases, it leads to a wasted execution because the user has to run the code again with warn log levels, just to cut out the noise and see their expected result.