apigear-io / cli

The ApiGear client as go project
https://apigear.io
MIT License
1 stars 2 forks source link

Ensure all filters transform names according to tech best practices #28

Open jryannel opened 1 year ago

jryannel commented 1 year ago

For example a filter used for params should provide same output for "value" or "Value" as input.

Reported was:


        params:
          - { name: SationName, type: string }```
Difference between what I used by now is that name of parameter starts with capital letter: StationName
so what I get when connecting singals using two filters;
```            [=]({{qtParams "" .Params}}) {
                const nlohmann::json& args = { {{ qtVars .Params }} };```
```            [=](const QString& sationName) {
                const nlohmann::json& args = { SationName };```
the problem is that the second filter should return same string as first, so either both give StationName or stationName

[Slack Message](https://epicgames.slack.com/archives/C03U8EPAKEG/p1675241476393949?thread_ts=1675241476.393949&cid=C03U8EPAKEG)