Fix obscure bug

[santib]

Having the status action defined in ApiController which is then inherited by other controllers, was causing a very strange bug related to the wrap_parameters Rails feature.

In order to reproduce go to the main branch, perform the following changes to force the execution of the wrap_parameters feature:

+++ spec/requests/api/v1/users/update_spec.rb
@@ -9,14 +9,14 @@ describe 'PUT api/v1/user/' do
   before { subject }

   context 'with valid params' do
-    let(:params) { { user: { username: 'new username' } } }
+    let(:params) { { username: 'new username' } }

     it 'returns success' do
       expect(response).to have_http_status(:success)
     end

     it 'updates the user' do
-      expect(user.reload.username).to eq(params[:user][:username])
+      expect(user.reload.username).to eq(params[:username])
     end

and run:

bundle exec rspec spec/requests/api/v1/status_spec.rb spec/requests/api/v1/users/update_spec.rb --order defined

as you can see it fails. The reason is that Rails is wrapping the parameters for the projects/update endpoint in a key named "api" instead of the correct one "user"

[JulianPasquale]

👀