SLF4J-256: Allow use of lambda to construct build event #278
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Rename current LoggingEventBuilder to FluentApiStub to better describe its responsibility - Rename NOPLoggingEventBuilder to NopFluentApiStub to align with new interface - New interface of LoggingEventBuilder to act only as Fluent Builder of LoggingEvent, which is used by the lambda
adrianshum
force-pushed
the
feature/SLF4J-256_LambdaForBuilder
branch
from
fa48d8a
to
3b24612
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
used by the lambda