Update from flow-php/flow@0d06018

Author: flow-php

changelog/index.html

@@ -379,10 +379,10 @@ <h2>Bridges</h2>
                 </a>
             </div>
 
-            <h1>Extension Points</h1>
+            <h1><a id="flow-php-extension-points" href="#content-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>Context</h2>
+<h2><a id="flow-php-context" href="#content-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>
@@ -399,7 +399,7 @@ <h2>Context</h2>
 <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>Decision</h2>
+<h2><a id="flow-php-decision" href="#content-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,
@@ -413,7 +413,7 @@ <h2>Decision</h2>
 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>Pros &amp; Cons</h2>
+<h2><a id="flow-php-pros--cons" href="#content-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>
@@ -422,14 +422,14 @@ <h2>Pros &amp; Cons</h2>
 <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>Alternatives Considered (optional)</h2>
+<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>
 <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>Links and References (optional)</h2>
+<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>
 <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>

documentation/adrs/extension-points/index.html

@@ -379,8 +379,8 @@ <h2>Bridges</h2>
                 </a>
             </div>
 
-            <h1>Architecture Decision Record</h1>
-<h1>What are ADRs?</h1>
+            <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>
 <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>
@@ -389,7 +389,7 @@ <h1>What are ADRs?</h1>
 <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>How to Use ADRs in This Project</h2>
+<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>
 <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>
@@ -401,14 +401,14 @@ <h2>How to Use ADRs in This Project</h2>
 <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>Index of ADRs</h2>
-<h3><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="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>
 <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 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 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="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>
 
 
             <hr class="!mt-8 !mb-8"/>

documentation/adrs/index.html

@@ -379,10 +379,10 @@ <h2>Bridges</h2>
                 </a>
             </div>
 
-            <h1>Static Analysis Baseline</h1>
+            <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>
 <p>Proposed by: <a rel="noopener noreferrer" target="_blank" href="https://github.com/norberttech">@norberttech</a>
 Date: 2025-01-07</p>
-<h2>Context</h2>
+<h2><a id="flow-php-context" href="#content-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>
@@ -401,21 +401,21 @@ <h2>Context</h2>
 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>Decision</h2>
+<h2><a id="flow-php-decision" href="#content-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>Pros &amp; Cons</h2>
+<h2><a id="flow-php-pros--cons" href="#content-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>Links and References</h2>
+<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>
 <hr />
 <ul>
 <li><a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/flow/issues/1329">#1329</a></li>

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

@@ -379,39 +379,39 @@ <h2>Bridges</h2>
                 </a>
             </div>
 
-            <h1>[Decision Title]</h1>
+            <h1><a id="flow-php-decision-title" href="#content-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>Context</h2>
+<h2><a id="flow-php-context" href="#content-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>Decision</h2>
+<h2><a id="flow-php-decision" href="#content-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>Pros &amp; Cons</h2>
+<h2><a id="flow-php-pros--cons" href="#content-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>Alternatives Considered (optional)</h2>
+<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>
 <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>Links and References (optional)</h2>
+<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>
 <hr />
 <blockquote>
 <p>Include any supporting documents, links to issues, pull requests, or discussions that provide context.</p>

documentation/adrs/template/index.html

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

documentation/components/adapters/avro/index.html

@@ -379,7 +379,7 @@ <h2>Bridges</h2>
                 </a>
             </div>
 
-            <h1>Chart JS Adapter</h1>
+            <h1><a id="flow-php-chart-js-adapter" href="#content-chart-js-adapter" class="mr-2" aria-hidden="true" title="Permalink">#</a>Chart JS Adapter</h1>
 <ul>
 <li><a href="../../introduction">⬅️️ Back</a></li>
 </ul>
@@ -394,10 +394,10 @@ <h1>Chart JS Adapter</h1>
 data visualization in large-scale and data-intensive environments. With Flow PHP's Adapter ChartJS, managing chart
 rendering and interaction within your ETL workflows becomes a more refined and efficient endeavor, harmoniously aligning
 with the robust and adaptable framework of the Flow PHP ecosystem.</p>
-<h2>Installation</h2>
+<h2><a id="flow-php-installation" href="#content-installation" class="mr-2" aria-hidden="true" title="Permalink">#</a>Installation</h2>
 <pre class="language-plain"><code class="language-plain" data-controller="syntax-highlight">composer require flow-php/etl-adapter-chartjs
 </code></pre>
-<h2>Usage</h2>
+<h2><a id="flow-php-usage" href="#content-usage" class="mr-2" aria-hidden="true" title="Permalink">#</a>Usage</h2>
 <pre class="language-php"><code class="language-php" data-controller="syntax-highlight">&lt;?php
 
 use function Flow\ETL\Adapter\ChartJS\{bar_chart, line_chart, pie_chart, to_chartjs_file, to_chartjs_var};

documentation/components/adapters/chartjs/index.html

@@ -379,7 +379,7 @@ <h2>Bridges</h2>
                 </a>
             </div>
 
-            <h1>CSV Adapter</h1>
+            <h1><a id="flow-php-csv-adapter" href="#content-csv-adapter" class="mr-2" aria-hidden="true" title="Permalink">#</a>CSV Adapter</h1>
 <ul>
 <li><a href="../../introduction">⬅️️ Back</a></li>
 </ul>
@@ -393,17 +393,17 @@ <h1>CSV Adapter</h1>
 making it a prime choice for developers dealing with CSV data in large-scale and data-intensive projects. With Flow
 PHP's Adapter CSV, managing CSV data within your ETL workflows becomes a more simplified and efficient task, perfectly
 aligning with the robust and adaptable framework of the Flow PHP ecosystem.</p>
-<h2>Installation</h2>
+<h2><a id="flow-php-installation" href="#content-installation" class="mr-2" aria-hidden="true" title="Permalink">#</a>Installation</h2>
 <pre class="language-plain"><code class="language-plain" data-controller="syntax-highlight">composer require flow-php/etl-adapter-csv
 </code></pre>
-<h2>Extractor</h2>
+<h2><a id="flow-php-extractor" href="#content-extractor" class="mr-2" aria-hidden="true" title="Permalink">#</a>Extractor</h2>
 <pre class="language-php"><code class="language-php" data-controller="syntax-highlight">&lt;?php
 
 $rows = data_frame()
     -&gt;read(from_csv($path))
     -&gt;fetch();
 </code></pre>
-<h2>Loader</h2>
+<h2><a id="flow-php-loader" href="#content-loader" class="mr-2" aria-hidden="true" title="Permalink">#</a>Loader</h2>
 <pre class="language-php"><code class="language-php" data-controller="syntax-highlight">&lt;?php
 
 data_frame()

documentation/components/adapters/csv/index.html

@@ -379,7 +379,7 @@ <h2>Bridges</h2>
                 </a>
             </div>
 
-            <h1>ETL Adapter: Doctrine</h1>
+            <h1><a id="flow-php-etl-adapter-doctrine" href="#content-etl-adapter-doctrine" class="mr-2" aria-hidden="true" title="Permalink">#</a>ETL Adapter: Doctrine</h1>
 <ul>
 <li><a href="../../introduction">⬅️️ Back</a></li>
 </ul>
@@ -394,12 +394,12 @@ <h1>ETL Adapter: Doctrine</h1>
 operations in large-scale and data-intensive environments. With Flow PHP's Adapter Doctrine, managing database
 interactions within your ETL workflows becomes a more simplified and efficient endeavor, perfectly aligning with the
 robust and adaptable nature of the Flow PHP ecosystem.</p>
-<h2>Installation</h2>
+<h2><a id="flow-php-installation" href="#content-installation" class="mr-2" aria-hidden="true" title="Permalink">#</a>Installation</h2>
 <pre class="language-plain"><code class="language-plain" data-controller="syntax-highlight">composer require flow-php/etl-adapter-doctrine
 </code></pre>
-<h2>Description</h2>
+<h2><a id="flow-php-description" href="#content-description" class="mr-2" aria-hidden="true" title="Permalink">#</a>Description</h2>
 <p>Adapter for <a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/etl">ETL</a> using bulk operations from <a rel="noopener noreferrer" target="_blank" href="https://github.com/flow-php/doctrine-dbal-bulk">Doctrine Dbal Bulk</a>.</p>
-<h2>Loader - DbalLoader</h2>
+<h2><a id="flow-php-loader---dballoader" href="#content-loader---dballoader" class="mr-2" aria-hidden="true" title="Permalink">#</a>Loader - DbalLoader</h2>
 <pre class="language-php"><code class="language-php" data-controller="syntax-highlight">data_frame()
     -&gt;read(from_())
     -&gt;write(new DbalLoader('your-table-name', $bulkSize = 100, ['url' =&gt; \getenv('PGSQL_DATABASE_URL')], ['skip_conflicts' =&gt; true]))
@@ -413,21 +413,21 @@ <h2>Loader - DbalLoader</h2>
 </ul>
 <p>The <code>bulkSize</code> means how many rows you want to push to a database in a single <code>INSERT</code> query. Each extracted rows set
 is going to be split before inserting data into the database.</p>
-<h2>Extractor - DbalQuery</h2>
+<h2><a id="flow-php-extractor---dbalquery" href="#content-extractor---dbalquery" class="mr-2" aria-hidden="true" title="Permalink">#</a>Extractor - DbalQuery</h2>
 <p>This simple but powerful extractor let you extract data from a single or multiple parametrized queries.</p>
-<h3>Single Query</h3>
+<h3><a id="flow-php-single-query" href="#content-single-query" class="mr-2" aria-hidden="true" title="Permalink">#</a>Single Query</h3>
 <pre class="language-php"><code class="language-php" data-controller="syntax-highlight">data_frame()
     -&gt;read(DbalQueryExtractor::singleQuery($connection, "SELECT * FROM {$table} ORDER BY id"))
     -&gt;write(to_())
     -&gt;run()
 </code></pre>
-<h3>Single Parametrized Query</h3>
+<h3><a id="flow-php-single-parametrized-query" href="#content-single-parametrized-query" class="mr-2" aria-hidden="true" title="Permalink">#</a>Single Parametrized Query</h3>
 <pre class="language-php"><code class="language-php" data-controller="syntax-highlight">data_frame()
     -&gt;read(DbalQueryExtractor::singleQuery($connection, "SELECT * FROM {$table} WHERE id = :id", ['id' =&gt; 1]))
     -&gt;write(to_())
     -&gt;run()
 </code></pre>
-<h3>Multiple Parametrized Query</h3>
+<h3><a id="flow-php-multiple-parametrized-query" href="#content-multiple-parametrized-query" class="mr-2" aria-hidden="true" title="Permalink">#</a>Multiple Parametrized Query</h3>
 <pre class="language-php"><code class="language-php" data-controller="syntax-highlight">data_frame()
     -&gt;read(
         new DbalQueryExtractor(
@@ -446,7 +446,7 @@ <h3>Multiple Parametrized Query</h3>
     -&gt;run()
 </code></pre>
 <p>In this case, query will be executed exactly five times, taking every time next entry of parameters from ParametersSet.</p>
-<h2>Schema Converter</h2>
+<h2><a id="flow-php-schema-converter" href="#content-schema-converter" class="mr-2" aria-hidden="true" title="Permalink">#</a>Schema Converter</h2>
 <p>With <code>to_dbal_schema_table()</code> function we can convert any Flow Schema (which represents a dataset)
 to Doctrine DBAL Schema Table.</p>
 <p>By providing metadata defined in <code>\Flow\ETL\Adapter\Doctrine\DbalMetadata</code> we can also add additional information to the schema,
@@ -510,7 +510,7 @@ <h2>Schema Converter</h2>
     ]
 );
 </code></pre>
-<h3>Schema Converter - Types Map</h3>
+<h3><a id="flow-php-schema-converter---types-map" href="#content-schema-converter---types-map" class="mr-2" aria-hidden="true" title="Permalink">#</a>Schema Converter - Types Map</h3>
 <p>When types map is not provided, the default one will be used:</p>
 <pre class="language-php"><code class="language-php" data-controller="syntax-highlight">public const DEFAULT_TYPES = [
     StringType::class =&gt; \Doctrine\DBAL\Types\StringType::class,