[php-laravel] Use baseName instead of paramName for request lookup & validation keys

[holkerveen]

Description

Hi there! Wanted to share one of the modifications we made to the php-laravel generator templates. This commit aims to fix a bug caused by case inconsistencies.

The php-laravel server templates read request values and build validation rules keyed by paramName — the sanitized PHP identifier — instead of baseName. Laravel does not convert casing though, so request variables do not get parsed correctly.

Example

Given a query parameter filter_name:

Before (generated — broken)

// In generated controller
$filterName = $request->string('filterName')->value(); // wire key is `filter_name` -> always null

Validator::make($request->all(), [
    'filterName' => ['string'],   // never matches the incoming `filter_name`
]);

After (generated — fixed)

$filterName = $request->string('filter_name')->value();

$validator = Validator::make($request->all(), [
    'filter_name' => ['string'],
]);

This is mostly a problem for form-data requests. application/json is handled using Serde (de)serializer and is unaffected.
PR is against master since it does not affect the interface other than fixing the actual bug.
Route parameters are not affected since these are resolved positionally. Intentionally did not change these so the generated interface classes are unaffected.

PR checklist

• Read the contribution guidelines.
• Run the following to build the project and update samples
• If your PR is targeting a particular programming language, @mention the [technical committee]
  @ybelenko @gijs-blanken

[cubic-dev-ai]

All reported issues were addressed across 9 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>