Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update compat date for cache: no-store. #3011

Merged
merged 1 commit into from
Oct 27, 2024

Conversation

AdityaAtulTewari
Copy link
Contributor

No description provided.

@AdityaAtulTewari AdityaAtulTewari merged commit cf2e60a into main Oct 27, 2024
13 checks passed
@AdityaAtulTewari AdityaAtulTewari deleted the AdityaAtulTewari/update-no-store-compat-date branch October 27, 2024 16:49
@@ -547,8 +547,8 @@ struct CompatibilityFlags @0x8f8c1b68151b6cef {
cacheOptionEnabled @53 :Bool
$compatEnableFlag("cache_option_enabled")
$compatDisableFlag("cache_option_disabled")
$experimental;
# Enables the use of no-cache and no-store headers from requests
$impliedByAfterDate(name = "cacheOptionEnabled", date = "2024-11-11");
Copy link
Member

@kentonv kentonv Oct 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to declare that cacheOptionEnabled implies itself. What does that mean?

AFAICT this doesn't do anything, it's basically saying: "After 2024-11-11, whenever cacheOptionEnabled is enabled, then cacheOptionEnabled should be enabled." But that's a tautology.

Did you mean to set $compatEnableDate instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes: #3014, my mistake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants