Composition in Multinode treepicker

[SandraGeisha]

The multinode treepicker allows you to pick document types that are used for compositions. For example we have a search composition that we include on a content page doctype. However when actually picking content it's not able to actually find content using this composition. It's quite counter intuitive. I suppose this is intended behaviour but in that case you shouldn't be able to pick the composition at all. The way we worked around it is by making a custom property editor and copying over the contentPickerController and view adding the following code to the init function:

     $scope.originalFilter = dialogOptions.filter;

        $scope.contentTypeResource.getAll().then(
            function (value) {
                var id = value.filter(v => v.alias === $scope.originalFilter)[0].id;
                $scope.contentTypeResource.getWhereCompositionIsUsedInContentTypes(id).then(
                    function (value) {
                        $scope.allowedDoctypes = value.map(v => v.contentType.alias);
                    }
                );
            }
        );

This enables us to find the doctypes that inherit from the composition and then in the scope.currentPicker function add the following to override the default filtering:

        $scope.currentPicker.filter = function (x) {
            return !$scope.allowedDoctypes.includes(x.metaData.contentType);
        }