I have a requirement to provide read-only access to member data and I have almost achieved this apart from one key property, the email address!

I have achieved most of what I need so far by using interceptors to replace the view urls with my own which reference my own controllers which extend the core ones rather than duplicating them. A simplified example as follows:

angular.module('umbraco.services').config([
    '$httpProvider',
    function($httpProvider) {

        $httpProvider.interceptors.push([
            '$q', '$injector', 'notificationsService', function($q, $injector, notificationsService) {
                return {
                    'request': function(request) {

                        // Redirect any requests to built in property editor and instead redirect to our own
                        if (request.url.indexOf("views/propertyeditors/textbox/textbox.html") === 0) {
                            request.url = '/App_Plugins/MyPlugin/PropertyEditors/securetextbox.html';
                        }

                        return request || $q.when(request);
                    }
                };
            }
        ]);

    }
]);

Any my custom controller as follows:

angular.module('umbraco').controller('MyPlugin.PropertyEditors.SecureTextboxController', function ($scope, $controller, memberDataAccessResource, $element) {

    memberDataAccessResource.hasAccess($scope.model.alias).then(function (result) {
        $scope.model.hasAccess = result;
    });

    angular.extend(this, $controller('Umbraco.PropertyEditors.textboxController',
        {
            $scope: $scope,
            $element: $element
        }));
});

This is an achievement in itself for me as I am no Angular expert! However, I am now at a roadblock with the email property as it using directive and unlike the other views which allow me to reference my own controller, I don't seem to have that luxury with a directive.

Can anyone offer some advice or potential solutions on how to tackle this, please?