fix: move global_fetch_strictly_public
to the correct folder
#22017
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.
Summary
This PR moves the description for
global_fetch_strictly_public
to the correct folder so that it appears at https://developers.cloudflare.com/workers/configuration/compatibility-flags/ (it did not appear anywhere before this PR)The original PR by @irvinebroque was opened in Nov 2024 when the description for the flags lived in
src/content/compatibility_dates
.After #18176, the description for the flags was moved to
src/content/compatibility_flags
, however #18075 was not updated to reflect the new location when it was merged 2 weeks ago.More information in the workerd repo
Screenshots (optional)
See https://vicb-fetch-public.preview.developers.cloudflare.com/workers/configuration/compatibility-flags/#global-fetch-strictly-public
Documentation checklist