>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3617842. --> Reported by: [ayalon](https://www.drupal.org/user/419226) Related to !70 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p><code>CoreComposableResolver::resolveItem()</code> turns every <code>uri</code>-typed field property (link fields, most notably) into a <code>Drupal\Core\Url</code> via <code>Url::fromUri()</code>. That method parses the query string with <code>UrlHelper::parse()</code>, which in turn uses PHP's <code>parse_str()</code>. <code>parse_str()</code> rewrites <code>.</code> and spaces in query parameter <em>names</em> to <code>_</code> &mdash; a leftover from the register_globals era. Consequently <code>Url.path</code> returns parameter names that differ from the ones stored in the field.</p> <p>A link field holding</p> <pre>entity:node/7?form.contact.subject=Order%20status&amp;form.contact.email=jane.doe%40example.com&amp;reset=1</pre><p>resolves through <code>Url.path</code> to</p> <pre>/the-alias?form_contact_subject=Order%20status&amp;form_contact_email=jane.doe%40example.com&amp;reset=1</pre><p>Note that only the parameter <em>names</em> are affected: <cod> became <code>form_contact_email</code>, while the dots inside the value <code>jane.doe@example.com</code> came through untouched. Percent-encoding is preserved as well, so the damage is easy to overlook when skimming a long URL.</cod></p> <p>Why this matters in practice: link fields are a natural way to point at an embedded third-party form and prefill it, and several form products namespace their prefill parameters with dots. The renamed parameters match no field in the target form, so it silently renders unprefilled &mdash; no error, no warning. Whatmakes it particularly hard to diagnose is that the value stored iect; only the resolved URL is mangled, so nothing in the editing UI hints at a problem.</p> <p>Two details worth noting:</p> <ul> <li>The mangling happens while the <code>Url</code> object is by cannot be recovered from the <code>Url</code> afterwards &mdash; a fixhas to keep the raw URI around.</li> <li>External URLs are <em>not</em> affected: they keep their raw query string, and their assembler merges the query option on top of it.</li> </ul> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Add a link field to any entity type and expose it through a core composable schema.</li> <li>Store a link whose query contains a dot in a parameter name, e.g. <code>entity:node/1?form.contact.email=test</code>.</li> <li>Query the field: <code>{ &hellip; { fieldLink { uri { path } } } }</code>.</li> <li><code>path</code> returns <code>?form_contact_email=test&lt;/cm.contact.email=test</code>.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Restoring the literal names unconditionally would be a behavioat already adapted to the mangled names, so make it opt-in with anew optional argument on <code>Url.path</code>:</p> <pre>path(preserveDots: Boolean = false): String</pre><p>Implementation in three small pieces:</p> <ol> <li>A new <code>UrlQueryHelper</code>. <code>rememberRawUri()</code> stores the URI a <code>Url</code> was built from in a namespaced URL option (inert for<br> URL generation &mdash; Drupal ignores unknown options). <pre>applyRawQnerated path and swaps its query section for the URI's originalquery string, verbatim, keeping any fragment.&lt;/li&gt;<br>&nbsp; &lt;li&gt;&lt;code&gt;CoreComposableResolver::resolveItem()</pre><p> calls <code>rememberRawUri()</code> when it builds the <code>Url</code>.</p></li> <li>A <code>core_schema_url_path</code> data producer replaces the <code>url_path</code> producer for <code>Url.path</code>. It behaves identically unless<br> <code>preserveDots</code> is <code>TRUE</code>.</li> </ol> <pre>public function resolve(Url $url, ?bool $preserveDots, Refinerface $metadata): string { $generated = $url-&gt;toString(TRUE); $metadata-&gt;addCacheableDependency($generated); $path = $generated-&gt;getGeneratedUrl(); return $preserveDots ? UrlQueryHelper::applyRawQuery($url, $path) : $path; }</pre><p>Taking the query over verbatim rather than re-parsing it means the encoding the editor entered survives byte for byte, and it needs no special cases for external URLs or for PHP's <code>a[b]=1</code> array syntax &mdash; both are simply passed through.</p> <p>One case does need care: outbound path processors receive <cod by reference and may>add parameters (a language query<br> parameter, for instance, when URL language negotiation is set to ing the query wholesale would drop those, so<br> <code>applyRawQuery()</code> diffs the generated query against th carries the additions over.</cod></p> <p>Verified behaviour (raw URI on the left, resolved <code>path(preserveDots: true)</code> on the right):</p> <pre>entity:node/7?form.a=x%20y&amp;n=1 -&gt; /alias?formstored https://ex.com/p?form.a=1&amp;c=2 -&gt; https://ex.com/p?form.a=1&amp;c=2 unchanged entity:node/7?a[b]=1&amp;c=2 -&gt; /alias?a[b]=1&amp;amm entity:node/7 -&gt; /alias unchanged entity:node/7?form.a=1#frag -&gt; /alias?form.a=1#fra entity:node/7?form.a=1 (+ processor) -&gt; /alias?form.a=1&amp;language=en addition kept</pre><h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Review the merge request.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None.</p> <h3 id="summary-api-changes">API changes</h3> <p>Additive only, no break:</p> <ul> <li><code>Url.path</code> gains an optional <code>preserveDots: Boolean = false</code> argument. Adding an argument with a default value is backwards compatible per the GraphQL specification, and existing queries tah as before. The argument is added to the <code>Url</code>,<br> <code>InternalUrl</code> and <code>EntityUrl</code> interfaces ans so it can be selected through any of them.</li> <li>New class<br> <pre>Drupal\graphql_core_schema\UrlQueryHelper&lt;/<br>&nbsp; &lt;li&gt;New data producer &lt;code&gt;core_schema_url_path</pre><p>. The <cer from>graphql is untouched and remains usable.</cer></p></li> </ul> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None.</p>