fix(cache): avoid warning if TURBO_FORCE, TURBO_REMOTE_ONLY, and TURBO_CACHE #9704
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.
Description
Previously we would erroneously warn users that
TURBO_REMOTE_ONLY
was being deprecated even if the correctTURBO_CACHE
was also present. This happened because we haveTURBO_FORCE
erase caching behavior and this was happening before we checked ifTURBO_REMOTE_ONLY
had a matchingTURBO_CACHE
declaration. The fix is just doing that check before doing the force override.Testing Instructions
Before
After: