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
#1759
This is sort of an oddball problem, since users probably have to try to hit this problem, but I reported it nonetheless.
More pane node names can be defined than make sense.
We might display a more meaningful error that hints at quoting if that resolves the issue or forbid certain names altogether.
I have tested this only with pane template names but I am sure there can be more places where these problems apply.
Basically the same case as with numbers, except now the special characters cause also trouble when they occur in the middle of the node name.
Quoting works again.
I haven't tested this exhaustedly, but I would guess there are a lot of special characters that may cause trouble.
The text was updated successfully, but these errors were encountered:
raphCode
changed the title
KDL strange node names
KDL: Problematic node names
Oct 19, 2022
raphCode
changed the title
KDL: Problematic node names
KDL layouts: Problematic node names
Oct 19, 2022
#1759
This is sort of an oddball problem, since users probably have to try to hit this problem, but I reported it nonetheless.
More pane node names can be defined than make sense.
We might display a more meaningful error that hints at quoting if that resolves the issue or forbid certain names altogether.
I have tested this only with pane template names but I am sure there can be more places where these problems apply.
Empty string
works, but that seems strange somehow
Numbers at the beginning
Kdl Deserialization Error
Quoting the second
0test
works.Plain number without letters are also affected.
Special characters
Failed to deserialize KDL node.
Basically the same case as with numbers, except now the special characters cause also trouble when they occur in the middle of the node name.
Quoting works again.
I haven't tested this exhaustedly, but I would guess there are a lot of special characters that may cause trouble.
The text was updated successfully, but these errors were encountered: