Remove document_capture_react_enabled configuration key#4154
Merged
Conversation
**Why**: As a developer, I want less ambiguity and fewer combinations of configuration keys, so that I can feel confident in knowing how to toggle the React-based document capture.
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
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.
Why: As a developer, I want less ambiguity and fewer combinations of configuration keys, so that I can feel confident in knowing how to toggle the React-based document capture.
This configuration key was originally added in #3994 to make it easier to test the fallback for the updated document capture flow. It is equally possible and more realistic to test this by disabling JavaScript in the browser (for example, using Chrome DevTools's Disable JavaScript setting).
Previously: