MDR UI: Do not allow spaces in the JSON name or uniqueName for MDR entities or attributes

[Jennifer-Oxborough]

Currently, the MDR UI allows spaces in the JSON name and uniqueName for MDR entities and attributes. This ticket is to remove that capability so that no spaces are allowed in the JSON name and uniqueName for MDR entities and attributes.

There is data clean up, and both front end and backend work tied to this effort:

• First: Data clean up via Remove spaces in the MDR entities' and attributes' fields of name and uniqueName #810
• Then MDR UI: Do not allow spaces in the JSON name or uniqueName for MDR entities or attributes #801 (this ticket) for UX hardening and MDR API: Do not allow spaces in the JSON name or uniqueName for MDR entities or attributes #811 for API hardening which can be done in parallel.

[cbeach47]

@ahungerford-unicon how big of an effort is this for the UX portion?

[ahungerford-unicon]

@ahungerford-unicon how big of an effort is this for the UX portion?

Should be relatively simple enough if we make it a universal rule for same field like Name and/or UniqueName, though this would affect all of the dialog modals since the only real rule we have is required which is the field is null or not. I think we may want to include a regex property which would make sure text fields follow the regex pattern rule, but we'd need to clarify what (if any) special, non-alphanumeric characters we'd want to allow as well; this would take a little bit more time, but would expand functionality and make it much more customization without overlaps.

We may also want back-end error checking as well just in case, especially for any File Import where the front-end wouldn't be able to do that kind of checking.

[ahungerford-unicon]

Added 810 as a Blocker to this ticket, but that is only true in that we want 810 completed before this ticket (801) gets merged.