feat: unit test and linting for cts generation APIC-277

[millotp]

🧭 What and Why

🎟 JIRA Ticket: APIC-277

Changes included:

• Check the linting for generation script in the CI
• Add unit test to the generation script
• Format the script at the end of generation to save time
• Clean up types for requests
• Recursive augmentation of parameters

🧪 Test

CI

[eunjae-lee]

can you explain to me what this enum type thing is? is it java related? if it is, what if we split data processing part per language? because this seems irrelevant to JS.

[millotp]

This is not just enum related, this will take all arguments like:

{
  "test1": "hello",
  "other": [{
    "test2": 4
  }]
}

And convert it to:

{
  "test1": {
    "value": "hello",
    "isArray": false,
    "isObject": false,
    "isInteger": false,
    "isString": true,
    ...
  },
  "other": {
    "value": [{
      "value": {
        "test2": {
           "value": 4,
           "isArray": false,
          "isObject": false,
          "isInteger": true,
          "isString": false,
          ...
        },
        "isArray": false,
        "isObject": true,
        "isInteger": false,
       "isString": false,
        ...
      },
      "isArray": false,
      "isObject": true,
      "isInteger": false,
      "isString": false,
      ...
    }],
    "isArray": true,
     "isObject": false,
     "isInteger": false,
     "isString": false,
      ...
  }
}

recursively, which is the common way to handle complex objects in mustache (openapi does the same augmentation).
This attribute parametersWithDataType will be the one used in all typed languages, the exception is actually js that don't need all that and can do fine just with the json representation.

[eunjae-lee]

Yeah, I saw that adds a bunch of helper variables for mustache. I was just wondering what removeEnumType function does :)

[millotp]

It's to remove all type decoration and leave raw json, for languages that don't support enum or don't need them