renderOptions may not be working

[naderafshari]

Command used:
ag asyncapi.yaml @lagoni/asyncapi-quicktype-template
-o output --param "quicktypeLanguage=cplusplus"
--param 'renderOptions={"memberNamingStyle":"camelValue"}'
--output ${CMAKE_CURRENT_BINARY_DIR} --force-write

Output from generator:
[ 26%] Invoking generator to generate AsyncAPI C++ files.
Generating files with options {
"parameters": {
"quicktypeLanguage": "cplusplus",
"renderOptions": "{"memberNamingStyle":"camelValue"}"
},
"quicktypeLanguage": "cplusplus",
"fileExtension": "cpp",
"generatorTargetDir": "/work/sgn-skeleton-cpp/_build/api/async",
"targetDir": "",
"renderOptions": {
"memberNamingStyle": "camelValue"
}
}
Rendering schema LinkStateChangeEvent with render options {
"memberNamingStyle": "camelValue"
}

Generated file:
class LinkStateChangeEvent {
public:
LinkStateChangeEvent() = default;
virtual ~LinkStateChangeEvent() = default;

    private:
    std::shared_ptr<std::string> correlation_id;
    std::shared_ptr<Data> data;
    std::shared_ptr<std::string> datacontenttype;
    std::shared_ptr<std::string> dataschema;
    std::shared_ptr<std::string> event_time;
    std::shared_ptr<std::string> id;
    std::shared_ptr<std::string> source;
    std::shared_ptr<std::string> specversion;
    std::shared_ptr<std::string> subject;
    std::shared_ptr<std::string> type;

As you can see member naming is not camel case. For example, eventTime instead of event_time

Is this a generator problem or a quicktype problem?

[jonaslagoni]

Hey @naderafshari, as I see it the options look like they are parsed correctly 🧐 There is no interpretations of the options, they are passed as is.

Are you sure the options are correct? I know that QuickType has some options that are not matched one-to-one and no real documentation to figure it out. You might need to look through the source code to make sure.

[jonaslagoni]

Hmm, I see that it should be accurate - https://github.com/quicktype/quicktype/blob/e6cc44fdfcb75c3f3ed3e12f69f15a0c863a1a05/src/quicktype-core/language/CPlusPlus.ts#L93

[jonaslagoni]

I think you are right it is a bug in here, the only way I see it can be fixed is to create our own option matching and creating accurate enum instances...