Using $translateProvider.useLoader, the addPart/refresh combination does not work properly for the frist element's translation.

Hi Pascal,

Here is the config

.config(['$translateProvider', '$translatePartialLoaderProvider', function ($translateProvider, $translatePartialLoaderProvider) {

    $translateProvider.useLoader('$translatePartialLoader', {
        urlTemplate: 'i18n/{lang}/{part}.json'
    });
    $translateProvider.preferredLanguage('en-EN');
    $translatePartialLoaderProvider.addPart('main');
}])

Tranlsation files are :- i18n/en-EN/main.json i18n/en-EN/pa.json i18n/fr-FR/main.json i18n/fr-FR/pa.json

The files have few common elements for example page heading is common in all files which refers to the heading of that particular page.

MainCtrl for mainview.html

angular.module('appApp')//organization-definition
    .controller('MainCtrl', ['$scope', '$translate', '$translatePartialLoader',
        function ($scope,   $translate, $translatePartialLoader) {            
            $translatePartialLoader.addPart('main');
            $translate.refresh();
        }
    ]);

PaAddCtrl for paview.html

angular.module('appApp')
    .controller('PaAddCtrl', ['$scope', '$translate', '$translatePartialLoader',
        function ($scope, $translate, $translatePartialLoader) {
            $translatePartialLoader.addPart('positions');
            $translate.refresh();
        }])

When the app starts, MainCtrl is the one so the language part sets up to main and it works fine. When I move to PaAddCtrl from MainCtrl, then the translation of first element does not come from the positions.json file but instead comes from the main.json file. And same thing happens when I move from PaAddCtrl’s paview.html to MainCtrl’s main.html.

What am I doing wrong? Can you please point it out and help me fix this?

[DWand]

@knalli, it seams that this issue is not resolved yet. I was unable to operate with the provided plunker. Also I did not look at the example on GitHub as it is huge and has a lot of directories.

But, there are at least two possible things which can lead to an unexpected behavior here.

1. Race condition between added parts in the loader. It can happen if different parts have some identical translation keys. Actually it is not the race condition here, but very similar and leads to unpredictable result. To solve this thing the developer has either to avoid a usage of identical translation ids or delete old parts before the refresh() method is called. Also, at the moment we have additional tools to help to fight this situation: the getRegisteredParts method and priority of the parts.
2. As for the question from stackoverflow, @gtbuchanan is right. There is a problem with synchronization between use() and refresh() methods.

[knalli]

Closed due inactivity. Enhancements for the partial loader already addressed in the linked issues.