Inconsistent parameters for user registration vs. user login

I agree with this issue. Please provide a patch. I am for shorter version 'name', 'pass'.

Patch won't pass tests. Please correct tests as well.

Id prefer that you used the versioning API that services provides so that this doesnt break peoples clients.

look at services.versions.api.php

yeah because if you change the user resource directly, peoples clients will break when they update Services.

As an example, this is in the user resource and lets admins choose the version they wish to use for the logout method.

<?php
/**
 *  Update the current user logout callback to the new callback with a better return value.
 */
function _user_resource_logout_update_1_1() {
  $new_set = array(
    'callback' => '_user_resource_logout_1_1',
  );
  return $new_set;
}

/**
 * Logs out the currently logged in user and returns the new user object.
 */
function _user_resource_logout_1_1() {
  global $user;

  if (!$user->uid) {
    // User is not logged in
    return services_error(t('User is not logged in.'), 406);
  }

  watchdog('user', 'Session closed for %name.', array('%name' => $user->name));

  // Destroy the current session.
  module_invoke_all('user_logout', $user);
  session_destroy();

  // Load the anonymous user.
  $user = drupal_anonymous_user();

  return $user;
}

#9: services-consistent-register-login-parameters-1975954-9.patch queued for re-testing.

I hate to be picky, but can we get a test for the new version response? Just create a total new test in the User resource.

leave the old one test intact, but make a new one, pass the version HEADER and verify that the parameters are correct and then this patch will be perfect.

You can see some examples in ServicesVersions.test and dont forget youll need to update the endpoint!

Heres a patch with tests.

Committed.