-
Notifications
You must be signed in to change notification settings - Fork 1.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
Performance optimizations #149
Comments
@jtomaszewski - Actually, I tried some of those ....
|
OK, I did most of it in my master branch. Can you check it out https://github.com/jtomaszewski/angular2-data-table , and either give me notes, what should I improve, or cherry-pick / merge all the commits ? (So I don't have to create a PR for each of them ;]). |
Hey, why did you close it? ;] There's still some commits here that can be merged: Should I do sepearte PRs for all of them? |
SorryI thought you said it was closed. I will manually merge them in :) |
The do check has to stay but I did the rest :) |
Thanks for the quick merging ;) Why does the doCheck has to stay? It's tempting to get rid of it as well. |
Its for when the columns change externally ( i think lol ) and one other thing I forgot. I will dig it up though and add comments. |
Closing as no longer relevant due to total onpush refactor. |
Is the angular2-data-table optimized when it comes to performance?
I didn't get to see through all the code, but after a quick glimpse:
trackBy
option to*ngFor="let row of rows; let i = index;"
inBody
component's templateBodyCell
,BodyRow
should propably be dependant only on Inputs and useChangeDetectionStrategy.OnPush
Body
propably could also useChangeDetectionStrategy.OnPush
, but as it's currently heavily dependant onStateService
, we would need to add some rxjs observables to that or something.What do you guys think? Maybe I could help a bit with that.
The text was updated successfully, but these errors were encountered: