When using the example for the firebase plugin, we get the following error from calling logWarning('Hello Warning');

[Firebase/Analytics][I-ACS013002] Event name must contain only letters, numbers, or underscores: Hello Warning
    ga_error_value (_ev) = Hello Warning;
    ga_error_value (_ev) = Hello Warning;
    ga_error_value (_ev) = Hello Warning;

I believe this is due to the fact that the message is passed as an event to firebase analytics.

The 3.0.0 release of the sentry package added web support: https://pub.dev/packages/sentry/changelog#300

sentry_lumberdash does not support the new sentry versions.

The term that is being used for describing the various implementations of lumberdash is plugin. Is this the correct terminology to be used? Shouldn't it be package instead? The term plugin in Flutter refers to libraries that include native calls to integrated platforms in which the application is being run on, where as package is for libraries that only include Dart code or interact with the Flutter framework libraries.
The overlap of the term definition can lead to confusion between non and Flutter developers.

As a result of #27 , we realized that the existing API is not as flexible as we thought it would be, and that it might be tailor made to Sentry.

Let's use this thread to propose a new/better API, and release a v2.

Requirements are:

• Ability to use multiple clients (simple, color, sentry, firebase...)
• Decide on a naming convention for the API
• Decide what's needed vs optional
• Better and complete documentation

Open questions:

• Should we separate plugins into its own repos?

@felangel @XinfengMa @erickjtorres FYI

Hey, I've seen that you don't actively maintain this project anymore. Are you open to pass over the ownership?

Version 3.0.0 with null safety is not available on pub.

Currently we can update lumberdash to 3.0.0 with null safety, but its pretty much useless, as plugins depend on lumberdash 2

This is a request to add support for null safety to package:lumberdash.
We depend on your awesome package, so would be great to have null safety enabled.

The Dart/Flutter team already encourages publishing the migrated packages: See this blog post.

See the migration guide for details about enabling null safety.

Description

The current JSON format is not really dev-friendly when debugging. The stack trace gets trimmed and, thus, it is almost useless.

Alternative

I was thinking of a format similar to the logger package, which I've already integrated within a local-personal plugin but if this feature were built-in, it would be great.

If you are ok with this proposal, I'd be glad to make a PR 😄.

ansicolor: ^1.0.2

Because {project} depends on firebase_lumberdash ^1.0.0 which depends on firebase_analytics ^2.1.1, firebase_analytics ^2.1.1 is required.
So, because {project} depends on firebase_analytics 3.0.0, version solving failed.

Is support possible for the latest Firebase Analytics package please?

Not sure how much the API has changed at all, but the lumberdash Firebase plugin is now unable to be used with the latest version of Firebase analytics.

# flutter pub get output
Because firebase_lumberdash >=2.0.0 depends on firebase_analytics ^5.0.2 and app depends on firebase_analytics ^6.0.0, firebase_lumberdash >=2.0.0 is forbidden.

I had the following code running without error until I upgraded firebase_luberdash.

logMessage('${bloc.runtimeType}: $event');

Now I am getting the following error:

E/FA      ( 6479): Name must consist of letters, digits or _ (underscores). Type, name: event, QuizBloc: Instance of 'InitializeQuiz'
E/FA      ( 6479): Invalid public event name. Event will not be logged (FE): MyBloc: Instance of 'InitializeAction'

I have narrowed it down to this commit, in which I see that the message passed for logging is now bound to the name property of FirebaseAnalytics client. The problem is that name comes with restrictions both in length (40) and it the character type (it only allows letters, digits or _).

I think a good solution, for now, would be to re-instate the loggerName.

https://pub.dev/packages/firebase_analytics

This is a request to add support for null safety to package:colorize_lumberdash and other packages.
We depend on your awesome package, so would be great to have null safety enabled.

The Dart/Flutter team already encourages publishing the migrated packages: See this blog post.

See the migration guide for details about enabling null safety.

Hi! I can´t printing properly in Visual Studio Code :( see:

Could you help me, please?

The page is trying to get an image from https://github.com/bmw-tech/lumberdash/raw/master/art/colorized.png, but the path doesn't exist

You probably should update the homepage in the pubspec.yaml of package:colorize_lumberdash, package:firebase_lumberdash, package:print_lumberdash, package:sentry_lumberdash so it points to this repo and not your fork of the repo!

Otherwise, when clicking on "View/Report issues" on pub.dev everyone will be redirected to the fork of the repo and NOT this repo.

As a developer, I'd like to have a client that can save logs to a local file

Hi,

Great library! Especially now supporting multiple loggers.

However I have a feature suggesting in that I would like to be able to only log certain levels of errors.
Ideally this level would be per logger but I guess the least impact would be in the main Lumberdash client.

Usecase:
Log error and fatal's to Crashlytics and the rest to the console.
Thanks

Paul

As a developer, there are instances where I want to use a no-op client and avoid generating any logs.

Because sentry_flutter >=6.0.0 <6.1.0-alpha.1 depends on sentry ^6.0.0 and sentry_flutter >=6.1.0-alpha.1 depends on sentry ^6.1.0-alpha.1, sentry_flutter >=6.0.0 requires sentry ^6.0.0. And because sentry_lumberdash >=3.1.0 depends on sentry ^5.0.0, sentry_lumberdash >=3.1.0 is incompatible with sentry_flutter >=6.0.0.

So, because sogogolf depends on both sentry_flutter ^6.0.0 and sentry_lumberdash ^3.1.0, version solving failed.
pub get failed (1; So, because sogogolf depends on both sentry_flutter ^6.0.0 and sentry_lumberdash ^3.1.0, version solving failed.)

Hi,

How can I have support for multiple plugins. For example I would like to use the Firebase and the Colorize plugin together so that logging is done to the console and also to FireBase