Fix: Properly parse custom array documentation #86
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.
This PR addresses the issue where
grape-swagger-entity
was not correctly parsing custom array documentation (e.g.,type: 'Array[Object]'
), leading to incorrect Swagger schema generation.The fix introduces a new
array_type?
method that intelligently identifies various array notations (is_array
,type: 'array'
, ortype: 'Array[Object]'
). This ensures that the documentation override is correctly recognized and that the generated Swagger schema accurately reflects the intended type.Part of [#962](ruby-grape/grape-swagger#962)