BREAKING CHANGE: Remove fallback_enabled option and error tuple from Split function results.
#26
Conversation
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
EmilianoSanchez
changed the title
fallback_enabled option and error tuple from Split function results.fallback_enabled option and error tuple from Split function results.
gthea
approved these changes
Feb 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fallback_enabledoption from theSplit.Supervisor.start_link/1function. The fallback behavior is now always enabled.Splitfunctions to never return{:error, _}tuples. Instead, they will use the fallback value when an error occurs (e.g.,"control"for get_treatment,falsefor track, etc).'exception', for consistency with other SDKs.