* GrapeSwagger::DocMethods::Extensions breaks the contract of
Kernel#method
This causes code inspection tools and development workflows to break
and may cause developers to choose not to use the gem.
* add test for method introspection on GrapeSwagger::DocMethods::Extensions
* fix ci lint failure
Previously this is what was generated:
`"attr":{"type":"array","items":{"type":"object","properties":{"":{"type":"string"}}}}`
instead of
`"attr":{"type":"array","items":{"type":"string"}}`
in case this attribute was nested in a Hash attribute with "body" in `param_type`
Previously the type from param definition would be used to documentation
even if we try to override it in the `documentation` hash.
It caused Swagger UI to render, for example, "Unknown Type: Color"
instead of using the provided entity.
It terms of code, before this change we would return something like this:
{ color: { type: 'Color' }
instead of:
{ color: { '$ref' => 'ColorEntity' }
if Color is not inherited from Grape::Entity
Having different types can be useful when two different classes
are used for parsing and presenting an attribute.
E.g. the input format for Base64 File can be represented as a Hash (content,
content_type and filename), whereas the type after parsing can be
ActionDispatch::Http::UploadedFile.
In the current situation the solution to this problem is to put coercion
methods to the same entity and specify `type` only for the param without
using `documentation`.
* Depply nested objects
* Simple hash syntax edit
* Nested objects are not necessary arrays
* fix points test
* Fix test services
* Doesn't require to delete hash or array properties
* Edit nested logic
* Add vehicle test
* Change parameter level is endpoint job
* Array body shouldn't lost array type
* no more parser role
* array of array to array of string
* move format data
* fix formdata return
* Moved params_parser role spec
* Move endpoint spec
* Revert "Add vehicle test"
This reverts commit e5ba63ba26.
* remove redundant interpolation
* Allow multiple success responses - Issue# 674
* Adding documentation in README for multiple values in success for response
* Making a slight change in the documentation
- updates dependencies
- looses rubocop dependency to minor
- adds 2.6.0-preview2 to travis
- adds grape 1.1.0 to travis
- skips testing of grape < 0.19.2
-> only have last three minors and HEAD
- updates dependencies
- looses rubocop dependency to minor
- adds 2.6.0-preview2 to travis
- adds grape 1.1.0 to travis
- skips testing of grape < 0.19.2
-> only have last three minors and HEAD
* Adds support for grape >= 1.2
Makes swagger backwards-compatible again
Adds a test that covers re-mounting with configuration
Describes changes on this PR
Removes custom branch from build process
* Upgrades Rubocop and autofixes indentation
* Locks rubocop version to 0.60
* Rollbacks version bump
* Removes HEAD from allowed failure
* Adds support for grape >= 1.2
Makes swagger backwards-compatible again
Adds a test that covers re-mounting with configuration
Describes changes on this PR
Removes custom branch from build process
* Upgrades Rubocop and autofixes indentation
* Locks rubocop version to 0.60
* Rollbacks version bump
* Removes HEAD from allowed failure
Tim Galeckas
Nick Bienko
Gwénaël Rault
peter scholz
charanpanchagnula
Olle Jonsson
Robert Schulze
Daniel Doubrovkine (dB.) @dblockdotorg
Edward Rudd
Fotos Georgiadis
Nicolas Klein
Lidiane Taquehara