[TypeError: Cannot convert undefined or null to object]

[justniels]

Every time i want to convert my generated .yaml or .json file i get this error.

[TypeError: Cannot convert undefined or null to object]

My file works with swagger ui and has just some warnings.

Link to my file: https://drive.google.com/open?id=0Bz6uStaBekRTOXYydVdTajlwNk0

[syroegkin]

It has a lot of warnings when I'm trying to check it here: http://editor.swagger.io/#/
But anyway that is interesting. I will take a look
thank you

[justniels]

Already took a look?

[jsundquist]

I just ran into the same issue this morning. The spec I have throws no warnings/errors within the swagger error. With out having a verbose output, the error message that is presented provides little to no way for me to trace what could be causing the issue. Any chance of adding some type of verbose output through each step to be able to determine where along the conversation line the error is occurring?

[dpavon]

Hi! I'm not sure if this problem is the same I had, but it kept appearing in:

• /swagger-markdown/bin/transformers/definitions.js

Following this: https://stackoverflow.com/questions/29721205/how-to-resolve-typeerror-cannot-convert-undefined-or-null-to-object, I just covered every "Object.keys" call to avoid that it executes with its contents in null, that is, checking both:

• "definition.properties" variable in "processDefinition"
• and "definitions" in module.exports a bit later.

I hope this helps someone, although I'm not sure if this is the right approach (maybe the expected swagger is missing something, even if we got it validated), but at least I got the markdown exported :)

(I'm using version 1.1.1, recently installed)

[syroegkin]

Sorry guys. I've been a little be lost.
Could I ask you again to share the yaml example where it is actually failing. So I would be able to fix an issue.
Thank you in advance
@dpavon

[adrienjoly]

Solved this problem by adding a properties: {} property after my allOf property, in the definition that was causing this error.

=>

  // [...]
  definitions: {
    // [...]
    PutConfigResponse: {
      allOf: [
        { $ref: '#/definitions/ResultObj' },
        { $ref: '#/definitions/UserActionObj' },
        {
          type: 'object',
          properties: { config: { $ref: '#/definitions/UserConfig' } },
        },
      ],
      properties: {}, // <-- new line that fixes the issue
    },
  },
  // [...]

That being said, it removes the error but does not render any property for my PutConfigResponse definition:

So I'm assuming that allOf is not supported by swagger-markdown, and that this PR may solve this problem: #94