-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix eager loading due to ServeStream rename #2072
Conversation
We can add a(n integration) spec for this, can't we? Calling |
Bump @stanhu want to finish this? |
a9f1236
to
0dd6ccc
Compare
@dblock Ok, done. |
0dd6ccc
to
fcafe0d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's still a need for a CHANGELOG line, this is a bug fix.
Errr... now looking into this I have more questions.
|
This issue also happens after calling: API.compile! So, we might use it in the integration test. |
@stanhu Want to finish so we can include this in the release? Let's include |
fcafe0d
to
bdc1dd9
Compare
@dblock I'm not sure if this is what you wanted, but take a look. |
ServeFile was renamed to ServeStream in ruby-grape#1520. Calling Grape.eager_load! would fail with: ``` uninitialized constant Grape::ServeFile (NameError) ```
bdc1dd9
to
09e3156
Compare
Made some changes and merged via b3adbb4. |
ServeFile was renamed to ServeStream in #1520. Calling Grape.eager_load!
would fail with: