Use AssetExecutionContext to correctly pass in StravaAPIResource #11
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.
Summary
I created a Dagster resource to abstract the Strava API in #5. However, it looks like I didn't implement its use correctly. This PR updates the implementation so that Dagster actually recognizes its use as a resource
Details
Before:
The
StravaAPIResource
I built it is not being recognized as a utilized assetThis is because I literally used it as a class object rather than using it as a Dagster resource through the
AssetExecutionContext
after passing the resource into theDefinitions
object.Note below that 'strava' has 0 uses.
After
The
StravaAPIResource
is now being recognizedAssetExecutionContext
allows an asset to use any resource that is defined in theDefinitions
object and call it throughcontext.resource
Note below that 'strava' has 2 uses.