-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
feat(query): implement ContentChildren and ViewChildren #4237
Conversation
594306a
to
3ac54f4
Compare
@@ -99,6 +112,7 @@ export class DirectiveResolver { | |||
exportAs: dm.exportAs, | |||
moduleId: dm.moduleId, | |||
compileChildren: dm.compileChildren, | |||
queries: queries, |
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.
did we consider having queries
and viewqueries
separately?
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.
Nevermind, there is no value is separating them.
|
||
private _createQueryRef(query: QueryMetadata): void { | ||
private _createQueryRef(dirIndex: number, setter: Function, query: QueryMetadata): void { |
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.
Replace Function
event with (any, any) => any
it will still provide a bit more typechecking, i.e. calling it with wrong number of args.
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.
Fixed it.
3ac54f4
to
fc1b410
Compare
Merging PR #4237 on behalf of @vsavkin to branch presubmit-vsavkin-pr-4237. |
fc1b410
to
b84a84e
Compare
Merging PR #4237 on behalf of @vsavkin to branch presubmit-vsavkin-pr-4237. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
@mhever @rkirov Could either of you review this guy?