We have added a new CodeGen setting that allows you to specify a list of words that Code Generation will not split when converting identifiers from API specification to language-specific identifiers. This is useful for declaring brand names such as APIMatic.
E.g. if you provide the words apimatic and vmware in your the list, APIMaticandvmWare becomes ApimaticAndVmware or apimatic_and_vmware, depending on the place of use.
Details
Going with the previous example of the list containing apimatic and vmware, language specific examples of converting APIMaticandvmWare to class/model/field names are given in the table below.
| Class Name | Method Name | Field Name | Argument Name | |
|---|---|---|---|---|
| Android | ApimaticAndVmware | apimaticAndVmware | apimaticAndVmware | apimaticAndVmware |
| C# | ApimaticAndVmware | ApimaticAndVmware | apimaticAndVmware | apimaticAndVmware |
| GO | ApimaticAndVmware | ApimaticAndVmware | apimaticAndVmware | apimaticAndVmware |
| Java | ApimaticAndVmware | apimaticAndVmware | apimaticAndVmware | apimaticAndVmware |
| NodeJS | ApimaticAndVmware | apimaticAndVmware | apimaticAndVmware | apimaticAndVmware |
| Obj-C | ApimaticAndVmware | apimaticAndVmware | apimaticAndVmware | apimaticAndVmware |
| PHP | ApimaticAndVmware | apimaticAndVmware | apimaticAndVmware | apimaticAndVmware |
| Python | ApimaticAndVmware | apimatic_and_vmware | apimatic_and_vmware | apimatic_and_vmware |
| Ruby | ApimaticAndVmware | apimatic_and_vmware | apimatic_and_vmware | apimatic_and_vmware |
The setting can be accessed in the editor as shown below.
