-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Add triggerer info to task instance in API #26249
Add triggerer info to task instance in API #26249
Conversation
ef4447b
to
54a7b37
Compare
Code makes sense to me. A few tests on the API and this should be good to go. |
54a7b37
to
f5a35c8
Compare
innerjoin=True, | ||
) | ||
|
||
trigger = relationship("Trigger", uselist=False) |
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.
Why don't we need innerjoin any longer?
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 think we ever needed it. not every TI has a trigger, so what happens is... when you reference this property in a query, the TIs that don't have a trigger drop out of the result set.
i looked, and it seems that there was only one usage of this attr, and in it, they actually overrided that setting, to set it to false...
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
7c0c0d9
to
5ba0be6
Compare
Showing triggerer info in a section at the top of grid view TI details section
section will only be visible when ti state is deferred