-
Notifications
You must be signed in to change notification settings - Fork 996
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
Subgraph Composition: Support multiple subgraph datasources #5731
base: krishna/sgc-multiple-sg-sources-fix
Are you sure you want to change the base?
Subgraph Composition: Support multiple subgraph datasources #5731
Conversation
56f041a
to
460f33e
Compare
6dfd085
to
a426a32
Compare
a426a32
to
c61b650
Compare
02ce854
to
62d1e2b
Compare
c61b650
to
8c2be00
Compare
5c14264
to
1ff44c6
Compare
1ff44c6
to
f43bf1b
Compare
} | ||
|
||
pub fn entity_type(&self) -> &str { | ||
self.entity.entity_type.as_str() | ||
} | ||
} | ||
|
||
impl Ord for TriggerData { | ||
fn cmp(&self, other: &Self) -> std::cmp::Ordering { | ||
match self.source_idx.cmp(&other.source_idx) { |
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 is somewhat important, I think would be worth some comments/documentation about the decision and why it is working this way. Also probably a simple test to ensure this assumption is not broken going forward
LGTM, really nice that you got added an integration test with the aggregation. |
No description provided.