You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When controller generator is used it generates a requests_spec file that is quite empty. It consists only of the describe .. do .. end block without any helping indication that the user can use stuff like expect(response).to have_http_status(200) like it happens when the simpler RequestSpecGenerator is used.
Describe the solution you'd like
when generating a controller the request spec generated will have a different file name and when it is generated without any action it will add just one spec for an index action with a message about adding a real spec.
Is your feature request related to a problem? Please describe.
When controller generator is used it generates a requests_spec file that is quite empty. It consists only of the
describe .. do .. end
block without any helping indication that the user can use stuff likeexpect(response).to have_http_status(200)
like it happens when the simpler RequestSpecGenerator is used.Describe the solution you'd like
when generating a controller the request spec generated will have a different file name and when it is generated without any action it will add just one spec for an index action with a message about adding a real spec.
Describe alternatives you've considered
TBD
Additional context
This issue is extracted from a wish in #2356
I had the idea that we can move the original PR along by separating the issues.
The text was updated successfully, but these errors were encountered: