leancodepl / leancodepl/flutter_corelibrary
[login_client] Use `package:logging` instead of a logger callback
Open
Nobody has claimed this yet.
p: login_client
- Dominant language
- Dart
- Stars
- 89
- Forks
- 12
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
Consider migrating from a simple void Function(String) for logging, and use the full Logger API.
- Currently, users of this package have no way of filtering logs (e.g., by severity)
- Using
Loggerwould provide a sane default configuration, instead ofprint() - The logs would contain exceptions and stack traces
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the login_client code that accepts the logger callback and review how its current print-based logging is configured. Check the package:logging API and dependency setup; done means logging uses Logger with severity filtering and preserves exceptions and stack traces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100