Rename render_page in apipie.rake to render_apipie_page #943
+6
−6
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.
We tried to integrate this project this week but ran into a very specific issue. We have a field called
render_page
on one of our models. And we're using factory_bot to build factories for our tests. Inside our factory we're calling arender_page
function to set up the data for the initial value. (i.e.)As soon as we add
apipie-rails
to the Gemfile like this it starts failing.Example output
I tracked it down to the fact that there is a function in
apipie.rake
that is aparantly existing in the global namespace and it's trying to call this function instead. I just renamed it to be very specific to apipie and I no longer have this issue.