brianegan / brianegan/new_flutter_template
Should the template set up logging?
- Dominant language
- Dart
- Stars
- 138
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Logging is one of those things every app will need sooner or later. Should it be set up in the template? To what extent?
* No logging in the template
* A comment in the appropriate place (`main()`) saying something like: "Here's where you can set up your logging and error reporting" (plus link)
* Use `pkg:logging` but do not gather the messages
* Use `pkg:logging` and gather the messages in `main` through `Logger.root.onRecord.listen`, printing them
* Use some other approach
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the template's main() entry point and review how pkg:logging and Logger.root.onRecord.listen would fit there. The issue presents several competing approaches but records no decision; done would require a maintainer-approved logging scope and an agreed implementation or documentation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile-dev, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100