Decouple endpoint resolution from http #455
Merged
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.
This decouples endpoint resolution from http. It does this by using the new
Endpointinterface that has a typed properties bag. HTTP endpoint providers MAY add a "headers" property that will be merged into the request's headers.The input of endpoint resolvers was simplified to be a standard param bundle that should contain anything they could possibly want. This includes the context properties for the invocation, so more stuff can be added there by interceptors. The config object is added as standard to the properties bag, but it's loosely typed since it's a generated type. The endpoint uri is added in a strongly typed way, though I had to play a bit fast and loose with pyright to get it to work with unions.
I also updated the formatting to remove unused imports because that makes the process of changing the default endpoint provider less painful.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.