Commits on Sep 25, 2017

1. Pre-calculate type aliases before processing models …

   A type alias in this context is where a model is simply another name for a
   primitive type, such as `MyString` in the following model definitions:
   
       MyList:
         type: array
         items:
           $ref: '#/definitions/MyString'
       MyString:
         type: string
   
   It is valid to use a type alias as a property in another object or array model,
   even if the object/array is defined before the alias is, as in the example
   above. However, the current alias logic only looks "back" in list of previously
   defined models, meaning that `MyList` would not know that `MyString` is an
   alias. This change fixes the incorrect behavior by pre-calculating the list of
   aliases before any models are processed. It also changes the test endpoint to
   verify the correct behavior even when an object is defined before an alias it
   uses.

   Benjamin Douglas committed Sep 25, 2017
   Configuration menu

   • View commit details
   • Copy full SHA for 31fc0a3
   • Browse repository at this point

   Copy the full SHA

   31fc0a3 View commit details

   Browse the repository at this point in the history