Proposal to change SelectArray plugin

[Antikon]

The SelectArray plugin has bad behavior, which leads to a change in the model attribute (see #439).
This behavior can be disabled by novel assignAfterFind option (#444). Howewer, this option disables autoconversion of data in a list view also.

I suggest changing renderList method of SelectArray or Select class and introducing new AngularJs directive selectArraySpan in the following way.

public function renderList($id, $ngModel)
    {
        if ($this->scheduling && $this->renderContext->canUpdate()) {
            return $this->createSchedulerListTag($ngModel, $this->getData(), 'item');
        }

        $options = Angular::optionsFilter([
            'options' => $this->getServiceName('selectdata'),
        ]);

        return $this->createTag('select-array-span', null, ArrayHelper::merge(['model' => $ngModel], $options));
    }

zaa.directive('selectArraySpan', function () {
    return {
        restrict: 'E', //E = element, A = attribute, C = class, M = comment
        scope: { //@ reads the attribute value, = provides two-way binding, & works with functions
            'model': '=',
            'options': '=',
            'optionsvalue': '@optionsvalue',
            'optionslabel': '@optionslabel',
        },
        controller: ['$rootScope', '$scope',  function ($rootScope, $scope) {
            if ($scope.optionsvalue === undefined) {
                $scope.optionsvalue = 'value';
            }
            if ($scope.optionslabel === undefined) {
                $scope.optionslabel = 'label';
            }

            $scope.getSelectedLabel = function () {
                // Keep raw value by default
                var selectedLabel = $scope.model;
                angular.forEach($scope.options, function (item) {
                    if ($scope.model == item[$scope.optionsvalue]) {
                        defaultLabel = item[$scope.optionslabel];
                    }
                });

                return defaultLabel;
            };
        }],


        template: function () {
            return '<span>{{getSelectedLabel()}}</span>';
        }
    };
});

I intentionally do not create PR, want to discuss first.

If such a solution does not find objection, I suggest changing a default behavior of SelectArray plugin in the next major version.

For now, we can inroduce SelectArray2 plugin, for example.

[nadar]

SelectArray was one of the first plugins in LUYA and is therefore used very often, so we should keep it like this, but i total agree, introducing a new/other SelectArray would be great. Maybe could name it dropdownSelect like yii active field does, but one of the big issues there is also: how to load the data and should the plugin auto observe/change the original value from the database.

[Antikon]

I don't mind "dropdownSelect" name.

The data is loaded via

$options = Angular::optionsFilter([
    'options' => $this->getServiceName('selectdata'),
]);

It will be updated each time we load or reload CRUD data through api request.

The displayed value in the CRUD list will change of course when the model changes someway.
In the CRUD create or update forms the form field will be the same as current in SelectArray plugin.

What about the name of AngularJs directive?

[Antikon]

Closed by #658