-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[graphql] instigation state by id #22543
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @alangenfeld and the rest of your teammates on Graphite |
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit e1a9fa7. |
@@ -281,13 +288,22 @@ class Meta: | |||
|
|||
instigationStateOrError = graphene.Field( | |||
graphene.NonNull(GrapheneInstigationStateOrError), | |||
instigationSelector=graphene.NonNull(GrapheneInstigationSelector), | |||
instigationSelector=graphene.Argument(GrapheneInstigationSelector), | |||
id=graphene.Argument(graphene.String), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this take an array of Ids instead so that I can use our batching abstraction :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i can on the "states" resolver -I need to add the database look impl for many by id so will be a stacked PR. Thought maybe converting "SingleXQuery` in place would be the move but I can see wanting to move to batching while we are changing things
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't mind keeping individual queries. It's likely faster since theres more parallelization, but also slight more taxing on the server. gcpu vs ux latency trade off
3c8fe6c
to
3677301
Compare
3677301
to
0b0fc9c
Compare
|
||
|
||
@dagster_model | ||
class CompoundID: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this name feels a little generic considering it's specific to instigators.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Repository
uses it too which is why i dropped instigator framing
open to other names tho
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CompoundExternalId
OriginAndSelectorId
meh, not user facing / changeable in the future since not persisted
0b0fc9c
to
1d08104
Compare
|
||
|
||
@dagster_model | ||
class CompoundID: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CompoundExternalId
OriginAndSelectorId
meh, not user facing / changeable in the future since not persisted
1d08104
to
e1a9fa7
Compare
CompoundID
to wrap external origin + selector id componentsSchedule
Sensor
andRepository
id fields to return serialized CompoundIDsinstigationStateOrError
to be able to fetch by idinstigationStatesOrError
and support fetching all instigation states by their containing repository IDHow I Tested These Changes
Added tests