Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provides utilities for customizing log output #107

Closed
myConsciousness opened this issue Apr 6, 2022 · 0 comments · Fixed by #110
Closed

Provides utilities for customizing log output #107

myConsciousness opened this issue Apr 6, 2022 · 0 comments · Fixed by #110
Assignees
@myConsciousness
Labels
Feedback: feature request I have a good idea Type: design

Comments

@myConsciousness
Copy link
Owner

1. Problem to solve

Provides utilities for customizing log output.

2. Proposal

Currently, only an abstract class is provided and customization of log output is left to the user, but we would like to provide utilities for common areas such as date/time and stack trace.

3. More information
@myConsciousness myConsciousness self-assigned this Apr 6, 2022
myConsciousness added a commit that referenced this issue Apr 7, 2022
@myConsciousness
feat: fix for the issue (#107)
3c781a7
@myConsciousness myConsciousness linked a pull request Apr 7, 2022 that will close this issue
feat: fix for the issue (#107) #110
Merged
7 tasks
bors bot added a commit that referenced this issue Apr 7, 2022
@bors @myConsciousness
Merge #110
9b95ac4 
110: feat: fix for the issue (#107) r=myConsciousness a=myConsciousness

# 1. Description

<!-- Provide a description of what this PR is doing.
If you're modifying existing behavior, describe the existing behavior, how this PR is changing it,
and what motivated the change. If this is a breaking change, specify explicitly which APIs have been
changed. -->

## 1.1. Checklist

<!-- Before you create this PR confirm that it meets all requirements listed below by checking the
relevant checkboxes (`[x]`). This will ensure a smooth and quick review process. -->

- [x] The title of my PR starts with a [Conventional Commit] prefix (`fix:`, `feat:`, `docs:` etc).
- [x] I have read the [Contributor Guide] and followed the process outlined for submitting PRs.
- [x] I have updated/added tests for ALL new/updated/fixed functionality.
- [x] I have updated/added relevant documentation in `docs` and added dartdoc comments with `///`.
- [x] I have updated/added relevant examples in `examples`.

## 1.2. Breaking Change

<!-- Does your PR require batch.dart users to manually update their apps to accommodate your change?

If the PR is a breaking change this should be indicated with suffix "!"  (for example, `feat!:`, `fix!:`). See [Conventional Commit] for details.
-->

- [ ] Yes, this is a breaking change.
- [x] No, this is _not_ a breaking change.

## 1.3. Related Issues

<!-- Provide a list of issues related to this PR from the [issue database].
Indicate which of these issues are resolved or fixed by this PR, i.e. Fixes #xxxx* !-->

<!-- Links -->

[issue database]: https://github.com/batch-dart/batch.dart/issues
[contributor guide]: https://github.com/batch-dart/batch.dart/blob/main/CONTRIBUTING.md
[batch.dart style guide]: https://github.com/batch-dart/batch.dart/blob/main/STYLEGUIDE.md
[conventional commit]: https://conventionalcommits.org


Co-authored-by: Kato Shinya <kato.shinya.dev@gmail.com>
@bors bors bot closed this as completed in #110 Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@myConsciousness myConsciousness

Labels
Feedback: feature request I have a good idea Type: design
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: fix for the issue (#107) myConsciousness/batch.dart
1 participant
@myConsciousness