You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of the properties are | undefined. Why? Is there a case where the queue would not have those properties? I think we would need 2 different types, one for request options which have mostly optional values but when you use request as a type you get from somewhere, all these will be populated by default values so the type should reflect that.
handledAt should be string | null as null is a value for in progress
The text was updated successfully, but these errors were encountered:
mtrunkat
added
t-platform
Issues with this label are in the ownership of the platform team.
t-tooling
Issues with this label are in the ownership of the tooling team.
and removed
t-platform
Issues with this label are in the ownership of the platform team.
labels
Mar 8, 2023
Can you list which ones? I can see loadedUrl, id, and headers, rest seems to be already mandatory. And I can already see why - the object represents a request, not necessarily processed - you don't know the loadedUrl or headers until you process it, I guess same applies for the id.
| undefined
. Why? Is there a case where the queue would not have those properties? I think we would need 2 different types, one for request options which have mostly optional values but when you use request as a type you get from somewhere, all these will be populated by default values so the type should reflect that.handledAt
should bestring | null
asnull
is a value for in progressThe text was updated successfully, but these errors were encountered: