SDK Connections - Include visual experiments and draft experiments by default #2103
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.
A common stumbling block for users is to create SDK Connections without the Visual Experiments toggle enabled. Later, when they reach out to support about their Visual Experiments not working, our first canned response is: 'Have you turned on visual experiments in your SDK connection?'
The reason a user want to omit visual experiments is to have a leaner payload to help with performance. Unfortunately, having this optimization by default is slowing down onboarding for new users.
This PR alters our SDK Connection creation modal so that when creating a new SDK Connection with the
'visualEditor'
capability, we default to having both fieldsincludeVisualExperiments
andincludeDraftExperiments
set totrue
.Users who wish to optimize still have the ability to do so. The assumption is that optimization will come later in the user journey and not in the initial onboarding phase for users.
This behavior does not apply to editing an SDK Connection - when editing, we maintain existing values, or set to false if the language selected no longer supports the
'visualEditor'
capability.