Update from flow-php/flow@e488b97

Author: flow-php

assets/manifest.json

@@ -148,7 +148,7 @@
     "wasm\/php.js": "\/assets\/wasm\/php-efe717082103712187d38a1e0aecf4a5.js",
     "wasm\/php.wasm": "\/assets\/wasm\/php-8f0f307bdd99263d3102236b035d9d5f.wasm",
     "wasm\/phpcsfixer.php.wasm": "\/assets\/wasm\/phpcsfixer.php-65bf51f1ea90e4896971e11e62efef0b.wasm",
-    "wasm\/tools\/flow.phar": "\/assets\/wasm\/tools\/flow-1cf7b41851c7d1b492cdab22569d21df.phar",
+    "wasm\/tools\/flow.phar": "\/assets\/wasm\/tools\/flow-1236d375074ea60e9ee028141484a77b.phar",
     "wasm\/tools\/php-cs-fixer.phar": "\/assets\/wasm\/tools\/php-cs-fixer-de55dbd75a08d2eac0f0435d4168e6bc.phar",
     "wasm\/vendor\/autoload.php.wasm": "\/assets\/wasm\/vendor\/autoload.php-901f7714ee4a437fea3a9d6638722933.wasm"
 }

…ow-1cf7b41851c7d1b492cdab22569d21df.phar …ow-1236d375074ea60e9ee028141484a77b.pharassets/wasm/tools/flow-1cf7b41851c7d1b492cdab22569d21df.phar renamed to assets/wasm/tools/flow-1236d375074ea60e9ee028141484a77b.phar assets/wasm/tools/flow-1cf7b41851c7d1b492cdab22569d21df.phar renamed to assets/wasm/tools/flow-1236d375074ea60e9ee028141484a77b.phar

@@ -478,7 +478,7 @@ <h2 class="text-xl mt-5">Description</h2>
                              class="rounded px-4 pt-4 overflow-auto shadow-2xl shadow-gray rounded border-gray border-2 relative mb-5"
                             data-controller="all-links-external"
                     >
-                        <h1><a id="flow-php-delete-rows-from-the-database-that-are-matching-rows-in-the-dataframe" href="#content-delete-rows-from-the-database-that-are-matching-rows-in-the-dataframe" class="mr-2" aria-hidden="true" title="Permalink">#</a>Delete rows from the database that are matching rows in the DataFrame.</h1>
+                        <h1><a id="delete-rows-from-the-database-that-are-matching-rows-in-the-dataframe" href="#delete-rows-from-the-database-that-are-matching-rows-in-the-dataframe" class="mr-2" aria-hidden="true" title="Permalink">#</a>Delete rows from the database that are matching rows in the DataFrame.</h1>
 <ul>
 <li><code>to_dbal_table_delete(...)</code></li>
 </ul>

changelog/index.html

@@ -478,7 +478,7 @@ <h2 class="text-xl mt-5">Description</h2>
                              class="rounded px-4 pt-4 overflow-auto shadow-2xl shadow-gray rounded border-gray border-2 relative mb-5"
                             data-controller="all-links-external"
                     >
-                        <h1><a id="flow-php-upsert-insert-or-update-data-into-a-database" href="#content-upsert-insert-or-update-data-into-a-database" class="mr-2" aria-hidden="true" title="Permalink">#</a>Upsert (insert or update) data into a database</h1>
+                        <h1><a id="upsert-insert-or-update-data-into-a-database" href="#upsert-insert-or-update-data-into-a-database" class="mr-2" aria-hidden="true" title="Permalink">#</a>Upsert (insert or update) data into a database</h1>
 <p>There are two ways to update data in the database:</p>
 <ul>
 <li><code>to_dbal_table_insert(...)</code></li>

data_frame/data_writing/database_delete/index.html

@@ -427,10 +427,10 @@ <h1 class="hidden lg:block">
                 </a>
             </div>
 
-            <h1><a id="flow-php-extension-points" href="#content-extension-points" class="mr-2" aria-hidden="true" title="Permalink">#</a>Extension Points</h1>
+            <h1><a id="extension-points" href="#extension-points" class="mr-2" aria-hidden="true" title="Permalink">#</a>Extension Points</h1>
 <p>Proposed by: <a rel="noopener noreferrer" target="_blank" href="https://github.com/norberttech">@norberttech</a><br />
 Date: 2025-01-09</p>
-<h2><a id="flow-php-context" href="#content-context" class="mr-2" aria-hidden="true" title="Permalink">#</a>Context</h2>
+<h2><a id="context" href="#context" class="mr-2" aria-hidden="true" title="Permalink">#</a>Context</h2>
 <hr />
 <p>Flow is a framework, and as all frameworks, it should provide extension points for developers to hook into the framework and extend its functionality.</p>
 <p>How to find an extension point?</p>
@@ -447,7 +447,7 @@ <h2><a id="flow-php-context" href="#content-context" class="mr-2" aria-hidden="t
 <p>Why? Because nothing prevents developers from extending those classes and injecting
 their custom version into the DataFrame.</p>
 <p>Those extension points can't be covered by our backward compatibility policy.</p>
-<h2><a id="flow-php-decision" href="#content-decision" class="mr-2" aria-hidden="true" title="Permalink">#</a>Decision</h2>
+<h2><a id="decision" href="#decision" class="mr-2" aria-hidden="true" title="Permalink">#</a>Decision</h2>
 <hr />
 <p><strong>Closed by default</strong></p>
 <p>All classes should be marked as <code>final</code> and whenever we need to expose an extension point,
@@ -461,7 +461,7 @@ <h2><a id="flow-php-decision" href="#content-decision" class="mr-2" aria-hidden=
 but we do not guarantee backward compatibility for those cases and everyone should
 do it at their own risk. As a Flow PHP maintainers, we also reserve the right to
 not provide any help or support for those cases.</p>
-<h2><a id="flow-php-pros--cons" href="#content-pros--cons" class="mr-2" aria-hidden="true" title="Permalink">#</a>Pros &amp; Cons</h2>
+<h2><a id="pros--cons" href="#pros--cons" class="mr-2" aria-hidden="true" title="Permalink">#</a>Pros &amp; Cons</h2>
 <hr />
 <ul>
 <li>zero risk of breaking accidentally backward compatibility promise</li>
@@ -470,14 +470,14 @@ <h2><a id="flow-php-pros--cons" href="#content-pros--cons" class="mr-2" aria-hid
 <li>easier to find an actual extension points</li>
 <li>impossible to mock classes that aren’t marked as <code>final</code> in tests (which is a good thing, users shouldn’t mock Flow classes in their test suites)</li>
 </ul>
-<h2><a id="flow-php-alternatives-considered-optional" href="#content-alternatives-considered-optional" class="mr-2" aria-hidden="true" title="Permalink">#</a>Alternatives Considered (optional)</h2>
+<h2><a id="alternatives-considered-optional" href="#alternatives-considered-optional" class="mr-2" aria-hidden="true" title="Permalink">#</a>Alternatives Considered (optional)</h2>
 <hr />
 <p>Alternatively we could take similar approach to Symfony and mark classes as <code>final</code>
 <a rel="noopener noreferrer" target="_blank" href="https://github.com/symfony/symfony/issues/15233#issuecomment-1566682054">when it makes sense</a>
 but this approach is too easy to get abused.</p>
 <p>Plus, changing non-final class into a final one is much bigger BC break
 then the other way around.</p>
-<h2><a id="flow-php-links-and-references-optional" href="#content-links-and-references-optional" class="mr-2" aria-hidden="true" title="Permalink">#</a>Links and References (optional)</h2>
+<h2><a id="links-and-references-optional" href="#links-and-references-optional" class="mr-2" aria-hidden="true" title="Permalink">#</a>Links and References (optional)</h2>
 <hr />
 <ul>
 <li><a rel="noopener noreferrer" target="_blank" href="https://ocramius.github.io/blog/when-to-declare-classes-final/">When to declare classes final</a></li>

data_frame/data_writing/database_upsert/index.html

@@ -427,8 +427,8 @@ <h1 class="hidden lg:block">
                 </a>
             </div>
 
-            <h1><a id="flow-php-architecture-decision-record" href="#content-architecture-decision-record" class="mr-2" aria-hidden="true" title="Permalink">#</a>Architecture Decision Record</h1>
-<h1><a id="flow-php-what-are-adrs" href="#content-what-are-adrs" class="mr-2" aria-hidden="true" title="Permalink">#</a>What are ADRs?</h1>
+            <h1><a id="architecture-decision-record" href="#architecture-decision-record" class="mr-2" aria-hidden="true" title="Permalink">#</a>Architecture Decision Record</h1>
+<h1><a id="what-are-adrs" href="#what-are-adrs" class="mr-2" aria-hidden="true" title="Permalink">#</a>What are ADRs?</h1>
 <p>Architecture Decision Records (ADRs) are structured documents that capture significant architectural decisions made during the development of this project.</p>
 <p>Each ADR explains:</p>
 <ul>
@@ -437,7 +437,7 @@ <h1><a id="flow-php-what-are-adrs" href="#content-what-are-adrs" class="mr-2" ar
 <li><strong>The consequences</strong>: The impact of the decision, both positive and negative.</li>
 </ul>
 <p>ADRs act as a single source of truth for important design and architectural choices, ensuring that everyone involved in the project has a shared understanding of why things are the way they are.</p>
-<h2><a id="flow-php-how-to-use-adrs-in-this-project" href="#content-how-to-use-adrs-in-this-project" class="mr-2" aria-hidden="true" title="Permalink">#</a>How to Use ADRs in This Project</h2>
+<h2><a id="how-to-use-adrs-in-this-project" href="#how-to-use-adrs-in-this-project" class="mr-2" aria-hidden="true" title="Permalink">#</a>How to Use ADRs in This Project</h2>
 <p><strong>Follow Existing ADRs</strong>: ADRs are mandatory to follow unless explicitly overridden by a new ADR. This ensures consistency in decision-making across the project.</p>
 <blockquote>
 <p>Whenever ADR is merged into the main branch, it is considered accepted and must be followed by all contributors.</p>
@@ -449,14 +449,14 @@ <h2><a id="flow-php-how-to-use-adrs-in-this-project" href="#content-how-to-use-a
 <li>Submit the ADR via a pull request and engage in a discussion with maintainers and contributors.</li>
 <li><strong>Document Decisions Transparently</strong>: All significant decisions must be documented. This includes not only what was decided but also the alternatives that were considered and why they were rejected.</li>
 </ul>
-<h2><a id="flow-php-index-of-adrs" href="#content-index-of-adrs" class="mr-2" aria-hidden="true" title="Permalink">#</a>Index of ADRs</h2>
-<h3><a id="flow-php-accepted-ad" href="#content-accepted-ad" class="mr-2" aria-hidden="true" title="Permalink">#</a><a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/flow/pulls?q=is%3Apr+is%3Aclosed+is%3Amerged+label%3AAD+">Accepted AD</a></h3>
+<h2><a id="index-of-adrs" href="#index-of-adrs" class="mr-2" aria-hidden="true" title="Permalink">#</a>Index of ADRs</h2>
+<h3><a id="accepted-ad" href="#accepted-ad" class="mr-2" aria-hidden="true" title="Permalink">#</a><a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/flow/pulls?q=is%3Apr+is%3Aclosed+is%3Amerged+label%3AAD+">Accepted AD</a></h3>
 <ul>
 <li><a href="/documentation/adrs/static-analysis-baseline">2025-01-07: Static Analysis Baseline</a></li>
 <li><a href="/documentation/adrs/extension-points">2025-01-09: Extension Points</a></li>
 </ul>
-<h3><a id="flow-php-proposed-ad" href="#content-proposed-ad" class="mr-2" aria-hidden="true" title="Permalink">#</a><a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/flow/pulls?q=is%3Apr+is%3Aopen+label%3AAD+">Proposed AD</a></h3>
-<h3><a id="flow-php-rejected-ad" href="#content-rejected-ad" class="mr-2" aria-hidden="true" title="Permalink">#</a><a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/flow/pulls?q=is%3Apr+is%3Aclosed+is%3Aunmerged+label%3AAD+">Rejected AD</a></h3>
+<h3><a id="proposed-ad" href="#proposed-ad" class="mr-2" aria-hidden="true" title="Permalink">#</a><a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/flow/pulls?q=is%3Apr+is%3Aopen+label%3AAD+">Proposed AD</a></h3>
+<h3><a id="rejected-ad" href="#rejected-ad" class="mr-2" aria-hidden="true" title="Permalink">#</a><a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/flow/pulls?q=is%3Apr+is%3Aclosed+is%3Aunmerged+label%3AAD+">Rejected AD</a></h3>
 
 
             <hr class="!mt-8 !mb-8"/>

documentation/adrs/extension-points/index.html

@@ -427,10 +427,10 @@ <h1 class="hidden lg:block">
                 </a>
             </div>
 
-            <h1><a id="flow-php-static-analysis-baseline" href="#content-static-analysis-baseline" class="mr-2" aria-hidden="true" title="Permalink">#</a>Static Analysis Baseline</h1>
+            <h1><a id="static-analysis-baseline" href="#static-analysis-baseline" class="mr-2" aria-hidden="true" title="Permalink">#</a>Static Analysis Baseline</h1>
 <p>Proposed by: <a rel="noopener noreferrer" target="_blank" href="https://github.com/norberttech">@norberttech</a>
 Date: 2025-01-07</p>
-<h2><a id="flow-php-context" href="#content-context" class="mr-2" aria-hidden="true" title="Permalink">#</a>Context</h2>
+<h2><a id="context" href="#context" class="mr-2" aria-hidden="true" title="Permalink">#</a>Context</h2>
 <hr />
 <p>After removal of Psalm and making PHPStan the main static analysis tool,
 we looked again into hardening the static analysis configuration.</p>
@@ -449,21 +449,21 @@ <h2><a id="flow-php-context" href="#content-context" class="mr-2" aria-hidden="t
 Whenever the code is changed, the baseline needs to be updated, which is an opportunity to also suppress new errors.<br />
 This means that maintainers would not only need to go through the code changes
 but also through the baseline file, which is not the best use of their very limited and valuable time anyway.</p>
-<h2><a id="flow-php-decision" href="#content-decision" class="mr-2" aria-hidden="true" title="Permalink">#</a>Decision</h2>
+<h2><a id="decision" href="#decision" class="mr-2" aria-hidden="true" title="Permalink">#</a>Decision</h2>
 <hr />
 <p>We <strong>must not</strong> use baseline for static analysis.
 Instead, errors can be suppressed by annotations in the codebase or globally
 in the static analysis tool configuration.</p>
 <p>Error suppression should be considered an edge case and should be used sparingly.
 Core contributors should review and approve all suppression annotations.</p>
-<h2><a id="flow-php-pros--cons" href="#content-pros--cons" class="mr-2" aria-hidden="true" title="Permalink">#</a>Pros &amp; Cons</h2>
+<h2><a id="pros--cons" href="#pros--cons" class="mr-2" aria-hidden="true" title="Permalink">#</a>Pros &amp; Cons</h2>
 <hr />
 <ul>
 <li>The codebase will be cleaner and more maintainable.</li>
 <li>More predictable and stricter types.</li>
 <li>Less maintenance overhead related to managing the baseline.</li>
 </ul>
-<h2><a id="flow-php-links-and-references" href="#content-links-and-references" class="mr-2" aria-hidden="true" title="Permalink">#</a>Links and References</h2>
+<h2><a id="links-and-references" href="#links-and-references" class="mr-2" aria-hidden="true" title="Permalink">#</a>Links and References</h2>
 <hr />
 <ul>
 <li><a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/flow/issues/1329">#1329</a></li>

documentation/adrs/index.html

@@ -427,39 +427,39 @@ <h1 class="hidden lg:block">
                 </a>
             </div>
 
-            <h1><a id="flow-php-decision-title" href="#content-decision-title" class="mr-2" aria-hidden="true" title="Permalink">#</a>[Decision Title]</h1>
+            <h1><a id="decision-title" href="#decision-title" class="mr-2" aria-hidden="true" title="Permalink">#</a>[Decision Title]</h1>
 <p>Proposed by: @author_github_username
 Date: YYYY-MM-DD</p>
-<h2><a id="flow-php-context" href="#content-context" class="mr-2" aria-hidden="true" title="Permalink">#</a>Context</h2>
+<h2><a id="context" href="#context" class="mr-2" aria-hidden="true" title="Permalink">#</a>Context</h2>
 <hr />
 <p><code>// Todo: Describe context here</code></p>
 <blockquote>
 <p>What is the current situation or issue that needs addressing?<br />
 Why is this decision necessary?<br />
 Any relevant background or constraints.</p>
 </blockquote>
-<h2><a id="flow-php-decision" href="#content-decision" class="mr-2" aria-hidden="true" title="Permalink">#</a>Decision</h2>
+<h2><a id="decision" href="#decision" class="mr-2" aria-hidden="true" title="Permalink">#</a>Decision</h2>
 <hr />
 <p><code>// Todo: Describe the decision here</code></p>
 <blockquote>
 <p>What is the decision being made?<br />
 State it clearly and concisely.</p>
 </blockquote>
-<h2><a id="flow-php-pros--cons" href="#content-pros--cons" class="mr-2" aria-hidden="true" title="Permalink">#</a>Pros &amp; Cons</h2>
+<h2><a id="pros--cons" href="#pros--cons" class="mr-2" aria-hidden="true" title="Permalink">#</a>Pros &amp; Cons</h2>
 <hr />
 <p><code>// Todo: Describe the consequences here</code></p>
 <blockquote>
 <p>What are the outcomes or implications of this decision?<br />
 Highlight both positive and negative impacts.</p>
 </blockquote>
-<h2><a id="flow-php-alternatives-considered-optional" href="#content-alternatives-considered-optional" class="mr-2" aria-hidden="true" title="Permalink">#</a>Alternatives Considered (optional)</h2>
+<h2><a id="alternatives-considered-optional" href="#alternatives-considered-optional" class="mr-2" aria-hidden="true" title="Permalink">#</a>Alternatives Considered (optional)</h2>
 <hr />
 <p><code>// Todo: Describe the alternatives here</code></p>
 <blockquote>
 <p>Briefly describe any alternatives that were considered.<br />
 Why were they not chosen?</p>
 </blockquote>
-<h2><a id="flow-php-links-and-references-optional" href="#content-links-and-references-optional" class="mr-2" aria-hidden="true" title="Permalink">#</a>Links and References (optional)</h2>
+<h2><a id="links-and-references-optional" href="#links-and-references-optional" class="mr-2" aria-hidden="true" title="Permalink">#</a>Links and References (optional)</h2>
 <hr />
 <blockquote>
 <p>Include any supporting documents, links to issues, pull requests, or discussions that provide context.</p>

documentation/adrs/static-analysis-baseline/index.html

@@ -427,7 +427,7 @@ <h1 class="hidden lg:block">
                 </a>
             </div>
 
-            <h1><a id="flow-php-avro-adapter" href="#content-avro-adapter" class="mr-2" aria-hidden="true" title="Permalink">#</a>Avro Adapter</h1>
+            <h1><a id="avro-adapter" href="#avro-adapter" class="mr-2" aria-hidden="true" title="Permalink">#</a>Avro Adapter</h1>
 <ul>
 <li><a href="/documentation/introduction">⬅️️ Back</a></li>
 </ul>