ConfigMapperInterface::populateFromRequest() has been changed to ::populateFromRouteMatch()

\Drupal\config_translation\ConfigMapperInterface::populateFromRequest() has been changed to \Drupal\config_translation\ConfigMapperInterface::populateFromRouteMatch(). In accordance with the new name it no longer takes a \Symfony\Component\HttpFoundation\Request $request argument, but a \Drupal\Core\Routing\RouteMatchInterface $route_match argument. Calling code needs to be adjusted, but anywhere a $request object is available a $route_match is also available (whereas the reverse is not true).

Implementors that override populateFromRequest() need to be adjusted as well. Note that mappers extending ConfigEntityMapper most likely should override the setEntity() method instead of the populateFromRouteMatch() method.

use Symfony\Component\HttpFoundation\Request;
use Drupal\Core\Routing\RouteMatchInterface;

// Before
function populateFromRequest(Request $request) {
  $some_value = $request->attributes->get('foo');
  // Do something with the value.
}

// After
function populateFromRouteMatch(RouteMatchInterface $route_match) {
  $some_value = $route_match->getParameter('foo');
  // Do something with the value.