-
Notifications
You must be signed in to change notification settings - Fork 346
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
Minor regression in types params names with 4.20240903.0
#2652
Comments
@jasnell Any idea what caused this regression? |
The last change seems to be |
No changes that I'm aware of that would cause this. Really odd. Could the formatting changes have broken the ast transform? |
@penalosa ... I think we should first rule out a regression in the type generation logic. If that points to a change on the runtime side, then we'll investigate further but there really hasn't been much here that could have changed as far as I know. |
It looks like this was partially resolved in the latest update:
|
Diff: https://npmdiff.dev/@cloudflare%2fworkers-types/4.20240821.1/4.20240903.0/package/experimental/index.ts
Raw diff: Cloudflare-Mining/Cloudflare-Datamining@66e9584#diff-498f7d22754cd92e5654b3be0adcae3df0c297abe440099d42dbc8cf43af66fd
FixedLengthStream
previously had named paramaters:Now these are more generic with just
param1
andparam2
:A few more methods/classes had the same thing occur including:
URL.canParse
URL.parse
IdentityTransformStreamQueuingStrategy
URLSearchParams
URLSearchParams.append
URLSearchParams.delete
URLSearchParams.get
URLSearchParams.getAll
URLSearchParams.has
URLSearchParams.set
The text was updated successfully, but these errors were encountered: