fix(cloudflare): Account for static fields in wrapper type #16303
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.
fixes #16247
By adjusting the generic, we'll make sure that we don't erase static fields with the
instrumentDurableObjectWithSentry
function. See an example below:By moving the
DurableObjectClass
into it's own generic (new (state: DurableObjectState, env: E) => T
), which we namedC
, it helps preserve the exact constructor type of the input class, including all its static properties and methods.This was previously being lost by not aligning the
DurableObjectClass
with the function return value.