fix(endpoint): normalize endpoint to string when passing from client config to endpointParams #4098
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.
Issue
#4076
#4095
Description
convert endpoint to string when passing from client config (where it may have been converted to a v1 endpoint by resolveEndpointConfig) to the
endpointParams
resolver input object.client.config.endpoint
can be a string, V1, or V2 endpoint objectresolveEndpointConfig
normalizes all of these to aProvider<Endpoint>
endpointParams
are generated from the config mapping instructions, the provider is resolved but the object is not converted to astring
, which is expected by the endpoints spec and ruleset.Testing