Uncaught TypeError when defining property named "type"

[dodgecm]

Hi,

First off, thanks so much for your hard work on the tool. I ran into an issue tonight with the most recent updates that I'd like to bring to your attention. Here's a very simple schema that triggers the parsing issue:

{
  "definitions": {

    "parentclass": {
      "type": "object",
      "properties": {
        "type" : { "type" : "string" }
      }
    },

    "subclass": {
      "$ref": "#/definitions/parentclass",
      "properties": {
        "type" : { "type" : "string", "template" : "broken" }
      }
    }
  },

  "title": "Broken Parsing Bug",
  "type": "object",
  "$ref": "#/definitions/subclass"
}

In the browser console, I get the following:
Uncaught TypeError: undefined is not a function

The stack trace points to this function in extendSchemas (line 688 or so):

extended.type = val.filter(function(n) {
   return obj2.type.indexOf(n) !== -1;
});

I hope this information is helpful. Please let me know if there's any other information I can provide, and thanks again for your work on this project.

-Chris

[jdorn]

I think this will require a rewrite of the extendSchemas function. It's confusing the property name "type" with the "type" keyword. Thanks for catching this.

In the mean time, if you use a property name other than "type" it should work (the property name "required" may break as well).