FEAT: parameterised headers rest_api_source #1
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.
Description
This pull request addresses the feature request discussed in issue dlt-hub#2071. It introduces dynamic parameter resolution for headers, allowing both keys and values to be resolved dynamically.
Key Features
Usage
The feature is demonstrated with the following example:
{ "name": "chicken", "endpoint": { "path": "chicken", "headers": {"{token}": "{token}", "num": "2"}, "params": { "token": { "type": "resolve", "field": "token", "resource": "authenticate", }, }, }, }
Tests
Comprehensive tests have been added to validate the implementation and ensure its correctness.