feat: Exposure logging toggle and WASM default#256
Merged
fabriziodemaria merged 5 commits intomainfrom Sep 12, 2025
Merged
Conversation
vahidlazio
approved these changes
Sep 12, 2025
31ef47f to
c9e2a1e
Compare
a6f39ec to
8c962d0
Compare
vahidlazio
approved these changes
Sep 12, 2025
This was referenced Sep 12, 2025
This file contains hidden or 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
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.
Users can opt out from Confidence internal logging in certain dev modes or testing scenarios. This prevents the SDK from generating exposure or resolve data in the backend side, while still allowing the test the resolving functionalities on the client side.
This also makes WASM the default resolution mode in the Local Provider