🚀 New talker feature in 2.1.0 release is filtering logs, exceptions and errors. Now I want to tell you how it works.

There can be a lot of logs in a large application. Working with network via http, local storage, controllers, exceptions, errors, verbose info, etc.

👀 Sometimes it becomes difficult to track something very important. And at this moment, the talker update is rushing to your aid.

⚙️ Filtering data with Talker

Let's imagine that there are a lot of logs in your application

But our interest is to see only navigation logs.
How we can make it?

Add filter to your Talker constructor, or set it by configure() method

  final talker = Talker(
    filter: BaseTalkerFilter(
      types: [TalkerRouteLog],
    ),
  );

  final talker = Talker();
  talker.configure(
    filter: BaseTalkerFilter(
      types: [TalkerRouteLog],
    ),
  );

types: - log types driven by Talker package or your custom logs that you create. How I can make custom log?

Result:

But, how can I make it if I do not know what type of log is it?
Talker can do it 🙂 Use titles: filed of filter

  final talker = Talker(
    filter: BaseTalkerFilter(
      titles: ['ROUTE'],
    ),
  );

Result will be same as of types: [TalkerRouteLog]

Thank you for reading post!
💻 Article example source code here

Show some ❤️ and put a star on the GitHub to support the project! We are trying to make the best logs and errors manager for Flutter applications.