You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the angular-translate site, the translate directive is a better option than the filter. It also may result in much more readable code, for example:
<span>{{ 'SOME.KEY' | translate }}</span><!-- versus --><spantranslate>SOME.KEY</span>
The performance of these two should be compared. In particular, we should pay attention to the number of $watchers on every page. If we can drastically reduce the number of $watchers, we should do a major overhaul and refactor the entire application.
This should probably be investigated as soon as possible. I'll look into it sometime this week.
The text was updated successfully, but these errors were encountered:
This commit modifies the tree and settings page to use the `translate`
directive instead of the translate filter. This result in an average
decrease of `$watchers` by 50%. The original page average was 648
`$watchers` with the tree fully expanded, but falls to 351 `$watchers`
by using the translate directive.
This commit determines the validity of IMA-WorldHealth#1074 and closesIMA-WorldHealth#1074.
This commit modifies the tree and settings page to use the `translate`
directive instead of the translate filter. This result in an average
decrease of `$watchers` by 50%. The original page average was 648
`$watchers` with the tree fully expanded, but falls to 351 `$watchers`
by using the translate directive.
This commit determines the validity of #1074 and closes#1074.
According to the angular-translate site, the translate directive is a better option than the filter. It also may result in much more readable code, for example:
The performance of these two should be compared. In particular, we should pay attention to the number of
$watchers
on every page. If we can drastically reduce the number of$watchers
, we should do a major overhaul and refactor the entire application.This should probably be investigated as soon as possible. I'll look into it sometime this week.
The text was updated successfully, but these errors were encountered: