Closed radeusgd closed 2 months ago
Refinement notes:
(
should be automatically closed, because we cannot handle it by wrapping in ()
[
should be handled with current tree-repair approach, because it should be limited by encircling ()
. But it still gives bad UX, because setting widget value to 8[
will create an application, effectively replacing number widget with some tree.So, the first two points should be done as a part of code widget. For this task, we should disallow number widget setting anything other than a number (at least until widget picker will be implemented - then we might be more flexible). Non-number values should be discarded.
By accident I typed
8'
in a number input widget and pressed enter.https://github.com/enso-org/enso/assets/1436948/10c1862b-7264-49d5-9ccb-2d96e204fea9
Actual behaviour
This led to the node becoming unparseable and display wrongly in the GUI.
Expected behaviour
The value should not be submitted, I probably should get some warning that
'
is not a valid character in the numeric input.Definitely the node should not become unparseable.