Add support for Edm.Untyped

[millicentachieng]

Fixes #511

[xuzhg]

Leave it an empty object? or use a 'type': 'object'?

[millicentachieng]

Suggested change

	"TripData": {},
	"TripData": {
	"type": "object"
	}

@andrueastman Your thoughts?

[andrueastman]

We should leave it as empty. The reason being that the data could be a primitive as well(integer, string ...) or even a collection. As the type is only known at runtime so I think it would be incorrect to allude that it's an object.

[millicentachieng]

Or we could have something like this (the list of types is not exhaustive):

components:
  schemas:
    ExampleResource:
      type: object
      properties:
        id:
          type: string
        customData:
          anyOf:
            - type: string
            - type: number
            - type: integer
            - type: boolean
            - type: object
            - type: array
              items:
                anyOf:
                  - type: string
                  - type: number
                  - type: integer
                  - type: boolean
                  - type: object

[garethj-msft]

Its not practical to model out everything it could be, as it could be a collection of structs each with a heterogeneous collection that's a mixture of bools, ints and more structs. So, as @andrueastman says, it's completely unknown at design time.

My JSON schema skill isn't strong, but appears that {} best expresses that complete lack of knowledge whether it is primitive, object or array.

[millicentachieng]

Thanks, @garethj-msft

[sonarqubecloud]

Quality Gate failed

Failed conditions
66.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud