Support semi-required parameters about twitter-api-client HOT 2 OPEN

Hi,
I think the suggested syntax is generic and flexible - gives you a room for combinations. But can also produce complex interfaces - and that might cost in implementation time.

I have another less-generic and less-complex suggestion IMO.
The assumption is a field can appear only once in the one-of-parameters section:

          parameters:
            - name: force_login
              description: Forces the user to enter their credentials to ensure the correct users account is authorized.
              required: false
              type: boolean
            - name: x
              description: Some description
              required: false
              type: string
          one-of-parameters: 
            - identification-options: 
              - name: user_id
                description: xxx
                type: number
              - name: screen_name
                description: yyy
                type: string

from twitter-api-client.

I think your suggestion is great for more complex scenarios.
Currently, I'm afraid to add further verbosity, since the yml spec files are already quite extensive.

I think a simple conditional statement will cover this use-case for now, and if we see the need for more complex conditional parameters (as the v2 endpoints develop), we will re-address this issue.

What do you think?

from twitter-api-client.