'type' is forced by bravado-core to be present in definitions about bravado-core HOT 4 CLOSED

Also, editor.swagger.io's petstore-simple has no type: object for all its definitions.

from bravado-core.

As per ron from swagger: it's not mandatory in schema definition, but it is highly recommended (I'll fix the examples). Not having a type has an unexpected meaning to most users.

from bravado-core.

The fix for #35 makes it so 'type' is required. The rationale being, definitions split up across multiple files are a little more involved to go track down and check for compliance. This is no longer just a matter of checking #/definitions in the root spec.

from bravado-core.

Why can't we just guess the type based on the given keywords if it is not defined?

http://json-schema.org/latest/json-schema-validation.html

e.g.
properties -> object
items -> array
else -> string

I'm using Restlet Studio for designing my API and it also doesn't generate these 'type' values.
(I already dropped them a mail, but I think there might be more tools which could make problems here)

from bravado-core.