Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Choosing the type of the expression is not trivial #39

Open
2 tasks
INazca opened this issue Mar 3, 2020 · 1 comment
Open
2 tasks

Choosing the type of the expression is not trivial #39

INazca opened this issue Mar 3, 2020 · 1 comment

Comments

@INazca
Copy link
Owner

INazca commented Mar 3, 2020

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

@INazca
Copy link
Owner Author

INazca commented Mar 8, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant