[Bug]: Allow for non-english characters where it should be allowed.

[erwangranger]

ODH Component

ODH Dashboard

Current Behavior

From https://issues.redhat.com/browse/RHODS-6346 and slack: https://redhat-internal.slack.com/archives/C03UGJY6Z1A/p1697115227770089

In various fields, it's possible to type in some non-english characters, but it then becomes impossible to save.

When saving, there is an error stating:

----
the object provided is unrecognized (must be of type Secret): 
couldn't get version/kind; json parse error: 
unexpected end of JSON input ({"apiVersion":"v1","kind":"Sec ...)

Some examples:

Expected Behavior

For each field where I can write text:

• Either the special characters are allowed, and they should be saved properly
• Or they are disallowed, and the application should clearly indicate it to the user, instead of failing to save.

Steps To Reproduce

here are some sample characters to test with:

à 
é
ł (unicode hex 0142) 
Ĥ (unicode hex 124)

Workaround (if any)

No response

What browsers are you seeing the problem on? (If applicable)

No response

Open Data Hub Version

RHODS 1.33

Anything else

No response

[lucferbux]

/transfer odh-dashboard

[andrewballantyne]

It appears this is done in YAML editor in OpenShift Console pretty straight forward. That might be the monaco editor and that might be the OpenShift Console. I don't think this needs-info anymore. We can manage these values however they do. Looks to be some conversation of the string.

[manosnoam]

This has been reported since RHODS 1.20... https://issues.redhat.com/browse/RHODS-7329.
This is now fixed in RHODS 2.4:
It is not allowed to enter unsupported Unicode characters in specified fields:

[manosnoam]

@andrewballantyne please note that this specific bug was resolved with a proper error message, but related bugs were not:
RHODS-12901 - No input validation when updating existing resource

RHODS-6346 - Missing input validation in item creation forms/fields