fix: omit endpoint polymorphs from resolved config types #1626
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.
EndpointResolvedConfig
is now universal for all clients. In it,endpoint?: Provider<Endpoint>
is declared.Because the input type of endpoint is
?: string | Provider<string> | Endpoint | Provider<Endpoint> | EndpointV2 | Provider<EndpointV2>
the resolved type combining theEndpointResolvedConfig
andClientResolvedEndpointParameters
is thenThis is confusingly verbose, and functionally equivalent to simply
Provider<Endpoint>
due to intersection. Omitting the field from the resolved config will allow the type to simply beProvider<Endpoint>
.