Fix CLI casing formatter flag --casing erroring with specific casings

[RichardAkman]

Current Behavior

Some casing flags result in an error due to containing whitespace and other characters that are invalid.

List of casing patterns that cause errors:

• CapitalCase
• DotCase
• NoCase
• PathCase
• SentenceCase

Expected Behavior

All casing formatter options should result in valid keys.

To Reproduce

Use any schema that has a key that contains more than 1 words, for example:

{
  "GREETING": {
    "type": "RegEx",
    "pattern": "^(hello|hey|welcome|hola|salute|bonjour|shalom|marhabaan)$",
    "default": "hello"
  },
  "SUBJECT": {
    "type": "String",
    "default": "world"
  },
  "USER_MESSAGE": {
    "type": "String",
    "template": "{{GREETING}}, {{SUBJECT}}!",
    "description": "Generates a full greeting message"
  }
}

Then use export with any of the mentioned casing formatters which will result in:

Error: invalid config key at ExportCommand:.ConfigKey:USER_MESSAGE, key "USER_MESSAGE" mustn't contain reserved words

Context

No response

[RichardAkman]

@rannn505 please give your opinion on handling this bug in a way that aligns with the product vision.

[hanshal101]

Hey @RichardAkman I would like to work on this issue. Can you walk me through this issue.

[Sadaf-A]

Hey @RichardAkman !
I would like to work on this issue

[RichardAkman]

Hi @Sadaf-A & @hanshal101, I'm really happy to see your enthusiasm. Currently, this issue is pending product input regarding how to go about solving it. Once we have a clearly defined approach that aligns with the product vision, I'll reach out and let you know that this issue is ready to be taken.