Repository navigation
Document Swagger metadata with the existing Representable parser - #47
Merged
Merged
Conversation
Danger ReportNo issues found. |
dblock
force-pushed
the
docs/swagger-representers-4
branch
from
October 27, 2026 10:34
9115180 to
8852539
Compare
dblock
force-pushed
the
docs/swagger-representers-4
branch
from
October 27, 2026 11:27
8852539 to
b0f3d70
Compare
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
dblock
force-pushed
the
docs/swagger-representers-4
branch
from
October 27, 2026 11:33
b0f3d70 to
477d1c4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #4.
Document optional grape-swagger-representable response schemas for Roar decorator classes. Put property types and descriptions in
documentation:, register the parser before adding Swagger routes, and use the same product representer for the response and schema. Use product-oriented example names (ProductRepresenter,ProductsAPI), explain parser/module limitations, and distinguish response documentation from request validation.Verified the exact README example with Grape 4.0.1, grape-swagger 2.2.0, and grape-swagger-representable 0.2.2: fetch the Swagger document before rendering any resource, assert its model reference and field types/descriptions, then verify the actual HTTP response. No duplicate parser or mandatory dependency changes.
Fix MongoDB 8.0 service startup failures on Linux 6.19+ by selecting Ubuntu 22.04 for those four matrix entries. Keep all seven Ruby/Mongoid/MongoDB/Grape combinations and coverage flags unchanged; other jobs retain their existing runners. Document the kernel restriction and runner selection.
AI-authored on behalf of @dblock.