Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow parsing Entity with no endpoint #12

Merged
merged 5 commits into from
Aug 2, 2016

Conversation

Lordnibbler
Copy link
Contributor

@Lordnibbler Lordnibbler commented Aug 1, 2016

In some cases, we want to document entities or response definitions separate from an endpoint. This allows us to generate documentation while passing an endpoint as nil.

@Lordnibbler
Copy link
Contributor Author

@mbleigh @dmitry review please :)

@dmitry
Copy link
Contributor

dmitry commented Aug 1, 2016

LGTM

@@ -1,69 +1,8 @@
require 'spec_helper'
require_relative '../../../spec/support/shared_contexts/this_api'
Copy link
Member

@dblock dblock Aug 1, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we not do this and require things through spec_helper or something via a "load everything from shared/*" first?

@Lordnibbler
Copy link
Contributor Author

@dblock I required everything in spec/support by default, can you re-review?

@dblock dblock merged commit 8e074eb into ruby-grape:master Aug 2, 2016
@dblock
Copy link
Member

dblock commented Aug 2, 2016

Looks good, merged.

@LeFnord
Copy link
Member

LeFnord commented Aug 5, 2016

for that, the model key exist 😉

@dblock
Copy link
Member

dblock commented Aug 5, 2016

What are you saying about this PR @LeFnord ?

@LeFnord
Copy link
Member

LeFnord commented Aug 6, 2016

@dblock … what I want to say is, that, if I understand the PR comment correct, this functionality exist in grape-swagger, see this API spec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants