Input/Output convention question. about cs-content

[orius123]

Hi,

the underscore convention comes from python,
there are people that write camelCase for variables in python but most doesn't..
so, moving to camel case will be better for Java, but since I believe most of our content will use Python personally I prefer underscores.

vote?

[meirwah]

i think all can agree on the underscore convention, BUT issue is what we do with inputs of the actions(which are java based)??

[orius123]

why not making operations that are java based use camelCase' andPython` based use underscores?

Java op

- java_op
    inputs:
      - firstInput
      - secondInput
    ....

Python op

- python_op
    inputs:
      - first_input
      - second_input
    ....

[meirwah]

👍 from my prespective...

[oritstone]

👍

[tudorlesan]

@orius123 @meirwah @oritstone there is one problem with this approach. Let's say we have a flow that has 2 steps that have as outputs error messages and an on_failure step which sends the error message as an email. If for example the first step will be a python_op then it would have the output error_message and the other one if it's a java_op it would have the output errorMessage. That means that everytime I have to check which one is not empty and email that one. The same for returnResult.Sounds good? WDYT?

[oritstone]

The problem with the different conventions between python & Java actions is only relevant in the operations, and each operation should be in a separate file.
When you specify an output to the operation, you can give whatever name you want, and it should be by our lower case words convention:

- java_op
    inputs:
      - firstInput
      - secondInput
    outputs:
      - error_message: errorMessage

And then in the flow, all the tasks deal with lower case names

[tudorlesan]

👍

[orius123]

feel free to close if you think it is resolved 😃