Set related to true when filtering
#44
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
milt
approved these changes
Aug 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Before, when filtering on non-Actor agents or non-Object activities, the query would fail to retrieve statements correctly because
related_agentsandrelated_activities, respectively, were not set totrue.In this mini-PR, we set those two params to
trueautomatically, even for Actor agents and Object activities. Partly because I'm not sure how to predicate on the agent/activity usage, but also because there may be cases where, for instance, an Object activity is also used as a Context activity in another statement. Thus, automatically settingrelatedtotrueallows for maximum flexibility.