# This is a combination of 2 commits.
# The first commit's message is:

feat (loaders): enable loaders cache

It useful if we disable cache in our project (for dynamic content), but want enable it for translation files (static content).
Also it useful if we need include translation into build file (cache in advance for production).

app.run(function($translationCache) {
    $translationCache.put('/compiled/module1/locals/en.json', '{"MODULE1.HELLO":"Hi!"}');
    // Other translations string added by Grunt
});
In conclusion, we never need uncached translations, because it is fixed content.

# This is the 2nd commit message:

feat (loaders): enable loaders cache

It useful if we disable cache in our project (for dynamic content), but want enable it for translation files (static content).
Also it useful if we need include translation into build file (cache in advance for production).

app.run(function($translationCache) {
    $translationCache.put('/compiled/module1/locals/en.json', '{"MODULE1.HELLO":"Hi!"}');
    // Other translations string added by Grunt
});
In conclusion, we never need uncached translations, because it is fixed content.
Merge branch 'canary' of github.com:angular-translate/angular-translate into feature/enable-cache

rs cache

It useful if we disable cache in our project (for dynamic content), but want enable it for translation files (static content).
Also it useful if we need include translation into build file (cache in advance for production).

app.run(function($translationCache) {
    $translationCache.put('/compiled/module1/locals/en.json', '{"MODULE1.HELLO":"Hi!"}');
    // Other translations string added by Grunt
});
In conclusion, we never need uncached translations, because it is fixed content.

# This is the 2nd commit message:

feat (loaders): enable loaders cache

It useful if we disable cache in our project (for dynamic content), but want enable it for translation files (static content).
Also it useful if we need include translation into build file (cache in advance for production).

app.run(function($translationCache) {
    $translationCache.put('/compiled/module1/locals/en.json', '{"MODULE1.HELLO":"Hi!"}');
    // Other translations string added by Grunt
});
In conclusion, we never need uncached translations, because it is fixed content.

# This is the 3rd commit message:

feat (loaders): enable loaders cache

It useful if we disable cache in our project (for dynamic content), but want enable it for translation files (static content).
Also it useful if we need include translation into build file (cache in advance for production).

app.run(function($cacheFactory) { var cache = $cacheFactory.get('$http');
    cache.put('/compiled/module1/locals/en.json', '{"MODULE1.HELLO":"Hi!"}');
    // Other translations string added by Grunt
});
In conclusion, we never need uncached translations, because it is fixed content.
feat (loaders): enable loaders cache

It useful if we disable cache in our project (for dynamic content), but want enable it for translation files (static
Also it useful if we need include translation into build file (cache in advance for production).

app.run(function($translationCache) {
    $translationCache.put('/compiled/module1/locals/en.json', '{"MODULE1.HELLO":"Hi!"}');
    // Other translations string added by Grunt
});
In conclusion, we never need uncached translations, because it is fixed content.