This is a little tasks, which should be picked up once CRUD (FERR-90, GithUb #13 ) is merged.
Currently the 'step 2' of the Query/View definition does not properly feedback. There are 2 problems The Submit button (after the CRUD merge those are called "Insert" or "Update" which are determined by $scope.buttonText)
The button should only go enable if at least 1 column is selected, however at least 1 output column should be active. A query without search fields is possible, but a query with a view without output data is useless.
There is no properly feedback why the button is disabled. The button should be enabled always, and feedback what is wrong need to be given if the button is pressed, or the button is disabled if invalid and then the fields should e.g. contain red borders with explanation mark tooltips or something.
This is a little tasks, which should be picked up once CRUD (FERR-90, GithUb #13 ) is merged.
Currently the 'step 2' of the Query/View definition does not properly feedback. There are 2 problems The Submit button (after the CRUD merge those are called "Insert" or "Update" which are determined by $scope.buttonText)
The button should only go enable if at least 1 column is selected, however at least 1 output column should be active. A query without search fields is possible, but a query with a view without output data is useless.
There is no properly feedback why the button is disabled. The button should be enabled always, and feedback what is wrong need to be given if the button is pressed, or the button is disabled if invalid and then the fields should e.g. contain red borders with explanation mark tooltips or something.