Camel case does not adjust path parameters

[jayvdb]

While path param names are internal to the spec doc, effectively only placeholders, having no bearing on actual use of the API, it is odd to use djangorestframework-camel-case and have snake case used for these path parameters while the rest of the spec uses camel case.

  /oscarapi/baskets/{basket_pk}/lines/{id}/:
    get:
      operationId: oscarapi_baskets_lines_retrieve
      description: |-
        Only the field `quantity` can be changed in this view.
        All other fields are readonly.
      parameters:
      - in: path
        name: basket_pk
        schema:
          type: integer
        required: true
      - in: path
        name: id
        schema:
          type: integer
        description: A unique integer value identifying this Cart line.
        required: true

[tfranzel]

@jayvdb i already prepared something. i would add one settings for camelizing both operationId and parameter names. that should make it consistent with djangorestframework-camel-case.

what do you think is better, camelize with capital first letter or not? basketPk or BasketPk , OscarapiBasketsLinesRetrieve or oscarapiBasketsLinesRetrieve. i think the serializer fields have no capital letter, so probably the latter, right?

[jayvdb]

Presumably this is part of the integration with djangorestframework-camel-case, so please be consistent with djangorestframework-camel-case , also called Dromedary case.

That would be basketPk and oscarapiBasketsLinesRetrieve.

The other one is Pascal case, and there are vanishing few uses of it.

[tfranzel]

@jayvdb please have a look and close if the new config CAMELIZE_NAMES works for you.

[jayvdb]

The tests that you wrote look good. Unfortunately I have diverged due to discarded PRs, so not worth time to set up testing of master.