use "virtualScrollTable" instead of MatTable class for referencing th… #110
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
…e MatTable (and possibly now also MatLegacyTable) in ContentChild()
|
Unfortunately, those changes will break base behavior, and will force all contributors to add I will provide normal fix for this issue soon |
|
Yeah. No problem. Thanks for work on it;) |
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.
…e MatTable (and possibly now also MatLegacyTable) in ContentChild()
adding #virtualScrollTable was my workaround for now to make it work with Angualr Material 15 (at least for MatLegacyTable) as well as 14.
Referencing by MatTable does not work in Angular Material 15 with legacy components because their class names have changed. I wasnt't able to test compatiblity to the new MDC MatTable yet.