You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The type of the expression was only chosen right by one user. Also it was not 100% clear to the users what they should type into the input field. It would be helpful for the users if they get suggestions or if they can only choose from a already given set of answers. This problem is not really leading to false answers, but it could cause problems with the discussion phase distribution, as almost every solution would be unique. For the UI this is only a "cosmetic" problem, but when linked to a completely functional backend it could lead to unwanted problems.
Solution:
add a picker instead of the input field
provide the picker with already given choices for the type
The text was updated successfully, but these errors were encountered:
Will not be implemented for the evaluation 2 prototype due to lack of time. Still this problem needs to be fixed in the future and is important to a full stack implementation.
The type of the expression was only chosen right by one user. Also it was not 100% clear to the users what they should type into the input field. It would be helpful for the users if they get suggestions or if they can only choose from a already given set of answers. This problem is not really leading to false answers, but it could cause problems with the discussion phase distribution, as almost every solution would be unique. For the UI this is only a "cosmetic" problem, but when linked to a completely functional backend it could lead to unwanted problems.
Solution:
add a picker instead of the input field
provide the picker with already given choices for the type
The text was updated successfully, but these errors were encountered: