Allow Classes for type declarations inside documentation #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Grape requires types to be specified using Classes, not strings. This was problematic when using Entity.documentation to specify params restrictions while also exposing the entity as a Model to grape-swagger.
Without this patch the above code causes grape-swagger to consider String distinct from 'string' when type checking for swagger output on Models. This breaks the swagger UI with "this.dataType.toLowerCase is not a function swagger"