feat(cli): mark sync-v2 parameters as safe and deprecate --x-* ones #935
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.
Motivation
On the previous release sync-v2 was available as "experimental" and was marked as "unsafe", our tests showed it ran really well, so in this release it is being marked as "safe", making it more user friendly to enable.
Acceptance Criteria
--x-sync-v2-only
and--x-sync-bridge
are still accepted but give a warning saying they're deprecated and will be removed in a later release (possiblyv0.60.0
)--sync-v2-only
and--sync-bridge
are added and have the same meaning as the--x-*
variants.--x-*
variants, meaning--x-sync-v2-only
and--sync-v2-only
can't be used at the same time, and as long as one of them is true, the value used is trueChecklist
master
, confirm this code is production-ready and can be included in future releases as soon as it gets merged