Add 2023-03-01 and 2023-07-01 types entrypoints#1057
Merged
Conversation
mrbbot
force-pushed
the
bcoll/types-extra-compat-dates
branch
from
9892b7f to
2246268
Compare
penalosa
approved these changes
Aug 25, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hey! 👋 This PR adds
@cloudflare/workers-typesentrypoints for compatibility dates2023-03-01and2023-07-01. These are the default on dates forhttp_headers_getsetcookieandurlsearchparams_delete_has_value_arg, both of which have user facing types changes. We're still planning to build a better system for this, that will allow users to generate types for any combination of compatibility dates and flags.