feat: logging requirements and logging hook #269
Merged
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
toddbaert
requested review from
justinabrahms,
moredip,
luizbon,
beeme1mr,
jonathannorris,
nicklasl,
hairyhenderson,
bacherfl,
askpt,
mschoenlaub,
kinyoklion,
Kavindu-Dodan,
aepfli,
luizgribeiro,
maxveldink,
andrewdmaclean,
lukas-reining and
james-milligan
beeme1mr
approved these changes
Aug 29, 2024
toddbaert
force-pushed
the
feat/logging
branch
from
0ae0cfb to
4319b54
Compare
Signed-off-by: Todd Baert <[email protected]>
toddbaert
force-pushed
the
feat/logging
branch
from
4319b54 to
dd59837
Compare
nicklasl
approved these changes
Aug 30, 2024
Signed-off-by: Todd Baert <[email protected]>
lukas-reining
approved these changes
Sep 3, 2024
aepfli
approved these changes
Sep 4, 2024
askpt
approved these changes
Sep 4, 2024
Yep! I've implemented one in Java now here: open-feature/java-sdk#1084 A |
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.
As discussed in recent meetings, we've had complaints about this from multiple sources. This PR adds a stipulation that no logging is done by the SDK during flag evaluation. It also defines a very simple
logging hookconcept as an included utility. These should be very simple to write and will provide all the needed logging but give authors more control than built in log statements. It will also be a very nice intro to the hooks concept for users.Here's the Java implementation: open-feature/java-sdk#1084