Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MUST property names must be ASCII camelCase [118a] - issues with objects #33

Open
dweber019 opened this issue Aug 15, 2022 · 0 comments

Comments

@dweber019
Copy link
Collaborator

Expected
The following component schema should trigger 118a as failed, as PageableRequest should be pageableRequest

components:
  schemas:
    PageableRequest:
      description: |
        request object to define how many items to select
      type: object
      properties:
        offsetId:
          description: |
            empty string for the first request or the value of 'nextOffsetId' of the last response
          type: string
        limit:
          format: int32
          description: |
            max items to be selected
          type: integer
      example:
        PageableRequest:
          offsetId: "xxx"
          limit: 3
    ContractList:
      description: |
        result object"
      type: object
      properties:
        nextOffsetId:
          description: |
            offset id of the last response used for paging (offsetId in the PageableRequest). If there are no more objects the offsetId will be an empty string
          type: string
        items:
          description: list of contracts activated for self-service
          type: array
          items:
            $ref: '#/components/schemas/SelfServiceContract'

Behavior
118a is not triggered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant