compony 0.11.12 → 0.11.13

data/doc/file.intents.html

@@ -60,7 +60,7 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Intents">Intents</h1>
+<h1 id="intents">Intents</h1>
 
 <p>An intent is a gateway to a component, along with relevant context. It encapsulates tools used to generate paths, checking <a href="/doc/guide/feasibility_md.html">feasibility</a> and rendering links and buttons pointing other components within your application.</p>
 
@@ -119,11 +119,11 @@
 <p>Any further arguments are passed to the initializer of the button if/when the intent gets rendered.</p>
 </li></ul>
 
-<h2 id="label-Helpers">Helpers</h2>
+<h2 id="helpers">Helpers</h2>
 
 <p>In practice, you will rarely call <code>Compony.intent</code> directly, and likely never <code>Compony::Intent.new</code>. Instead, you will be interacting with one of the following helpers that will instanciate an intent under the hood and thus all accept similar arguments as those described above:</p>
 
-<h3 id="label-Compony.path"><code>Compony.path</code></h3>
+<h3 id="componypath"><code>Compony.path</code></h3>
 
 <p>This helper is useful when generating paths without rendering any HTML, such as when redirecting. Internally, this builds an intent which will in turn use the target component’s <code>path</code> block to generate a Rails path (String) pointing to the correct location. Any keyword arguments are passed to the intent’s <code>path</code> method, allowing you to override the model (to refer to <a href="/doc/guide/resourceful_md.html">resourceful</a> target components), as well as specifying a <code>standalone_name</code> or pass extra arguments to the target component’s <code>path</code> block.</p>
 
@@ -135,7 +135,7 @@
 </span><span class='id identifier rubyid_redirect_to'>redirect_to</span> <span class='const'><span class='object_link'><a href="Compony.html" title="Compony (module)">Compony</a></span></span><span class='period'>.</span><span class='id identifier rubyid_path'><span class='object_link'><a href="Compony.html#path-class_method" title="Compony.path (method)">path</a></span></span><span class='lparen'>(</span><span class='symbol'>:step_2</span><span class='comma'>,</span> <span class='symbol'>:registrations</span><span class='comma'>,</span> <span class='label'>accept_terms:</span> <span class='symbol'>:yes</span><span class='rparen'>)</span> <span class='comment'># Redirects to something like /registrations/step_2?accept_terms=yes
 </span></code></pre>
 
-<h3 id="label-render_intent"><code>render_intent</code></h3>
+<h3 id="renderintent"><code>render_intent</code></h3>
 
 <p>This is the preferred way of quickly rendering <a href="#buttons-and-styles">links or buttons to components</a> from other parts of your application. The method is implemented twice:</p>
 <ul><li>
@@ -155,7 +155,7 @@ end
 
 <p>In the example above, there is a lot more going on than it seems. Due to the <a href="#buttons-and-styles">specified style</a>, a plain HTML link will be generated, pointing to the component <code>Components::Users::Show</code> and instanciating it with the first user as <code>@data</code>. Assuming that component inherits from <code>Compony::Components::Show</code> and did not override label or path, the link will be labelled “Show” (which is the default short format label generated by Compony’s default <a href="/doc/guide/pre_built_components/show_md.html">pre-built Show component</a>), and the <code>href</code> will be <code>/users/:id</code> where ID will automatically be <code>User.first</code>‘s ID (e.g. <code>/users/1</code>). However, if <code>:show</code> was <a href="/doc/guide/feasibility_md.html">prevented</a>, the link will be strikethrough, non-clickable, greyed out and have a title explaining why it can’t be clicked. Further, if the current user does not have <a href="/doc/guide/standalone_md.html">authorization</a> to display the target user, the link will not show up at all, and no HTML will be generated within the <code>div</code>.</p>
 
-<h3 id="label-render_sub_comp"><code>render_sub_comp</code></h3>
+<h3 id="rendersubcomp"><code>render_sub_comp</code></h3>
 
 <p>This is used within a component’s <code>content</code> block to instanciate another component and <a href="/doc/guide/nesting_md.html">nest it within</a>. Internally, the current component’s <code>sub_comp</code> method is used and all arguments are passed to that.</p>
 
@@ -173,13 +173,13 @@ end
 
 <p>This implicitely builds an intent which auto-detects the family name <code>:quotes</code> from <code>@data.quotes</code>, which is an active record collection and thus implements <code>model_name</code>. The List component is then instanciated with its <code>@data</code> being that very collection and the users’s Show component as <code>parent_comp</code>, resulting in the proper nesting and display of the desired resources.</p>
 
-<h3 id="label-Compony.comp_class_for"><code>Compony.comp_class_for</code></h3>
+<h3 id="componycompclassfor"><code>Compony.comp_class_for</code></h3>
 
 <p>This helper is useful for checking whether a component is implemented. For instance, when implementing <a href="/doc/guide/inheritance_md.html">abstract components to inherit from later</a>, you can check for <code>if Compony.comp_class_for(:destroy, family_name)</code> to only provide some functionality of a Destroy component exists for the current family.</p>
 
 <p>This method also has its sibling <code>Compony.comp_class_for!</code>, which will fail if no such component could be found. It is however mostly used internally.</p>
 
-<h2 id="label-Buttons+and+styles">Buttons and styles</h2>
+<h2 id="buttons-and-styles">Buttons and styles</h2>
 
 <p>Button components are used as presenters for intents, hyperlinks to other components or submit buttons. They are a central way to define how buttons all over the application should look like. Their interface is adapted to intents, creating a standardized “slim waist” that greatly simplifies linking between components. Note that the term “button” refers to how they look and not how they are actually implemented - actual HTML buttons have several disadvantages (e.g. requiring drop-in forms and not responding to Ctrl+Click or middle-click when the user would prefer a new tab).</p>
 
@@ -207,7 +207,7 @@ end
 
 <p>Note: it is possible to use a button component to submit a form. In order to achieve this, you must implement a hidden submit button (for handling keyboard Enter and Return), as well as pass <code>onclick: &quot;this.closest(&#39;form&#39;).requestSubmit(); return false;&quot;</code> as an argument. See the pre-built Form component’s implementation for an example.</p>
 
-<h3 id="label-Adding+your+own+styles">Adding your own styles</h3>
+<h3 id="adding-your-own-styles">Adding your own styles</h3>
 
 <p>In your application, you will likely want to implement your own button styles. Create a component (e.g. <code>Components::Commons::MyButton</code>) and inherit from <code>Compony::Components::Buttons::Link</code>. Override the method <code>prepare_opts!</code> and don’t forget to call <code>super</code> first. Then, go through any <code>@comp_args</code> that might be of interest to you and mutate <code>@comp_args[:style]</code> and/or <code>@comp_args[:class]</code> to suit your needs. Make sure to handle the class <code>disabled</code>, as intents will set them if the intent is not feasible. Note that if a user is lacking authorization to perform an intent, the intent will not even instanciate the button.</p>
 
@@ -215,7 +215,7 @@ end
 
 <p>If you have multiple kinds of buttons (e.g. dropdown items, pill-style buttons, compact forms etc.), you should create a separate style and button component class for every kind. This will make it easy to refer to them by supplying something like <code>style: :dropdown_item</code> in <code>render_intent</code>.</p>
 
-<h2 id="label-Exposed+intents">Exposed intents</h2>
+<h2 id="exposed-intents">Exposed intents</h2>
 
 <p>Components can expose a set of intents to be displayed elsewhere. Those can either be rendered by the parent comp, or by the application layout itself in case the component exposing them is currently <code>root_comp</code> (see the chapter about <a href="/doc/guide/standalone_md.html">standalone</a>). This is useful if you have something like an actions toolbar that changes depending on the currently contained component.</p>
 
@@ -240,7 +240,7 @@ end
 
 <p>Note that the <code>add</code> method has full intent argument support and thus also accepts parameters related to the button (e.g. <code>style</code>), path generation, feasibility etc.</p>
 
-<h3 id="label-Rendering+exposed+intents">Rendering exposed intents</h3>
+<h3 id="rendering-exposed-intents">Rendering exposed intents</h3>
 
 <p>You can render exposed intents in the parent component or in the application layout. To do so, call <code>component.exposed_intents</code>, loop across them and call <code>.render(controller)</code> on each (perhaps inside a <code>div</code> tag or whatever suits your needs).</p>
 
@@ -255,7 +255,7 @@ end
 </div></div>
 
       <div id="footer">
-  Generated on Tue Jun 30 22:41:18 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.internal_datastructures.html

@@ -60,11 +60,11 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Internal+datastructures">Internal datastructures</h1>
+<h1 id="internal-datastructures">Internal datastructures</h1>
 
 <p>Compony has a few internal data structures that are worth mentioning. Especially when building your own UI framework on top of Compony, these might come in handy.</p>
 
-<h2 id="label-MethodAccessibleHash">MethodAccessibleHash</h2>
+<h2 id="methodaccessiblehash">MethodAccessibleHash</h2>
 
 <p>This is a simpler and safer version of <a href="https://github.com/ruby/ostruct">OpenStruct</a>, allowing you to access a hash’s keys via method accessors.</p>
 
@@ -77,11 +77,11 @@
 </span><span class='id identifier rubyid_options'>options</span><span class='period'>.</span><span class='id identifier rubyid_color'>color</span> <span class='comment'># =&gt; green
 </span></code></pre>
 
-<p>This part of Compony is also made available under the MIT license at: <a href="https://gist.github.com/kalsan/87826048ea0ade92ab1be93c0919b405">gist.github.com/kalsan/87826048ea0ade92ab1be93c0919b405</a>.</p>
+<p>This part of Compony is also made available under the MIT license at: <a href="https://gist.github.com/kalsan/87826048ea0ade92ab1be93c0919b405">https://gist.github.com/kalsan/87826048ea0ade92ab1be93c0919b405</a>.</p>
 
-<h2 id="label-RequestContext">RequestContext</h2>
+<h2 id="requestcontext">RequestContext</h2>
 
-<p>The content blocks, as well as Form’s <code>form_fields</code> block all run within a <code>Compony::RequestContext</code>, which encapsulates useful methods for accessing data within a request. RequestContext is a Dslblend object and contains all the magic described in <a href="https://github.com/kalsan/dslblend">github.com/kalsan/dslblend</a>.</p>
+<p>The content blocks, as well as Form’s <code>form_fields</code> block all run within a <code>Compony::RequestContext</code>, which encapsulates useful methods for accessing data within a request. RequestContext is a Dslblend object and contains all the magic described in <a href="https://github.com/kalsan/dslblend">https://github.com/kalsan/dslblend</a>.</p>
 
 <p>The main provider (refer to the Dslblend documentation to find out what that means) is set to the component. Additional providers are controller’s helpers, the controller itself, as well as custom additional providers that can be fed to RequestContext in the initializer.</p>
 
@@ -119,7 +119,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Tue Jun 30 22:41:19 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.list.html

@@ -63,13 +63,13 @@
 <p><a href="/doc/guide/pre_built_components_md.html">List of pre-built components</a></p>
 </li></ul>
 
-<h1 id="label-Pre-built+components-3A+List">Pre-built components: List</h1>
+<h1 id="pre-built-components-list">Pre-built components: List</h1>
 
-<p><code>Compony::Components::List</code> is a resourceful component that renders a table/list of records. It is <strong>not</strong> standalone — it is meant to be nested, typically inside href="./index_md.html"></a> of the same family or href="./show_md.html"></a> of an owning family, via <code>render_sub_comp(:list, collection)</code>.</p>
+<p><code>Compony::Components::List</code> is a resourceful component that renders a table/list of records. It is <strong>not</strong> standalone — it is meant to be nested, typically inside <a href="./index_md.html"><code>Index</code></a> of the same family or <a href="./show_md.html"><code>Show</code></a> of an owning family, via <code>render_sub_comp(:list, collection)</code>.</p>
 
 <p>Features: field-inferred or custom columns, per-row intents, pagination, and — when the <a href="https://github.com/activerecord-hackery/ransack">Ransack</a> gem is present and at least one sort/filter is declared — sorting links, a sort select, and a filter/search form.</p>
 
-<h2 id="label-Column+DSL">Column DSL</h2>
+<h2 id="column-dsl">Column DSL</h2>
 
 <table role="table">
 <thead>
@@ -81,18 +81,18 @@
 </thead>
 <tbody>
 <tr>
-<td>‘column`</td>
-<td>‘column(:name, label: nil, class: nil, link_opts: {}) { |record| … }`</td>
-<td>Add/define a column. No block → model-field column (auto label, value via ‘value_for`, only if `:index` permitted). Block is instance-exec’d per row and renders the cell.</td>
+<td><code>column</code></td>
+<td><code>column(:name, label: nil, class: nil, link_opts: {}) { |record| ... }</code></td>
+<td>Add/define a column. No block → model-field column (auto label, value via <code>value_for</code>, only if <code>:index</code> permitted). Block is instance-exec’d per row and renders the cell.</td>
 </tr>
 <tr>
-<td>‘columns`</td>
-<td>‘columns(:a, :b, as_title: false, **kw)`</td>
-<td>Bulk ‘column`. `as_title: true` marks title columns (shown as the card heading in mobile/card layouts).</td>
+<td><code>columns</code></td>
+<td><code>columns(:a, :b, as_title: false, **kw)</code></td>
+<td>Bulk <code>column</code>. <code>as_title: true</code> marks title columns (shown as the card heading in mobile/card layouts).</td>
 </tr>
 <tr>
-<td>‘skip_column`</td>
-<td>‘skip_column(:name)`</td>
+<td><code>skip_column</code></td>
+<td><code>skip_column(:name)</code></td>
 <td>Hide a (possibly inherited) column.</td>
 </tr>
 </tbody>
@@ -109,7 +109,7 @@
 <span class='kw'>end</span>
 </code></pre>
 
-<h2 id="label-Filtering+-26+sorting+-28Ransack-29">Filtering &amp; sorting (Ransack)</h2>
+<h2 id="filtering--sorting-ransack">Filtering &amp; sorting (Ransack)</h2>
 
 <table role="table">
 <thead>
@@ -121,28 +121,28 @@
 </thead>
 <tbody>
 <tr>
-<td>‘filter`</td>
-<td>‘filter(:name, label: nil) { |f| … }`</td>
-<td>Add a filter. No block → field filter or a Ransack predicate string (e.g. ‘:id_eq`). Block gets the Ransack search form and renders label + input.</td>
+<td><code>filter</code></td>
+<td><code>filter(:name, label: nil) { |f| ... }</code></td>
+<td>Add a filter. No block → field filter or a Ransack predicate string (e.g. <code>:id_eq</code>). Block gets the Ransack search form and renders label + input.</td>
 </tr>
 <tr>
-<td>‘filters`</td>
-<td>‘filters(:a, :b, **kw)`</td>
-<td>Bulk ‘filter`.</td>
+<td><code>filters</code></td>
+<td><code>filters(:a, :b, **kw)</code></td>
+<td>Bulk <code>filter</code>.</td>
 </tr>
 <tr>
-<td>‘sort`</td>
-<td>‘sort(:name, label: nil)`</td>
+<td><code>sort</code></td>
+<td><code>sort(:name, label: nil)</code></td>
 <td>Add a sort criterion (must be Ransack-sortable). Generates one sort link + asc/desc entries.</td>
 </tr>
 <tr>
-<td>‘sorts`</td>
-<td>‘sorts(:a, :b)`</td>
-<td>Bulk ‘sort`.</td>
+<td><code>sorts</code></td>
+<td><code>sorts(:a, :b)</code></td>
+<td>Bulk <code>sort</code>.</td>
 </tr>
 <tr>
-<td>‘default_sorting`</td>
-<td>‘default_sorting(’id desc’)‘</td>
+<td><code>default_sorting</code></td>
+<td><code>default_sorting(&#39;id desc&#39;)</code></td>
 <td>Default Ransack sort applied when none chosen.</td>
 </tr>
 </tbody>
@@ -158,7 +158,7 @@
 <span class='kw'>end</span>
 </code></pre>
 
-<h2 id="label-Per-row+intents">Per-row intents</h2>
+<h2 id="per-row-intents">Per-row intents</h2>
 
 <p><code>row_intents</code> opens the <a href="/doc/guide/intents_md.html#exposed-intents">intent management DSL</a> (<code>add</code>/<code>remove</code>, <code>before:</code>) applied to each row’s record:</p>
 
@@ -170,7 +170,7 @@
 <span class='kw'>end</span>
 </code></pre>
 
-<h2 id="label-Toggles-2C+paging-2C+styling">Toggles, paging, styling</h2>
+<h2 id="toggles-paging-styling">Toggles, paging, styling</h2>
 
 <p>All have matching constructor kwargs so a nesting parent can override per render (<code>render_sub_comp(:list, coll, skip_pagination: true, skip_columns: [:order])</code>).</p>
 
@@ -184,27 +184,27 @@
 </thead>
 <tbody>
 <tr>
-<td>‘pagination(bool)`</td>
+<td><code>pagination(bool)</code></td>
 <td>on</td>
 <td>Enable/disable paging (off loads all rows).</td>
 </tr>
 <tr>
-<td>‘results_per_page(n)`</td>
+<td><code>results_per_page(n)</code></td>
 <td>20</td>
 <td>Rows per page.</td>
 </tr>
 <tr>
-<td>‘filtering(bool)`</td>
+<td><code>filtering(bool)</code></td>
 <td>on</td>
 <td>Enable/disable the filter form.</td>
 </tr>
 <tr>
-<td>‘sorting(bool)` / `sorting_in_filter(bool)` / `sorting_links(bool)`</td>
+<td><code>sorting(bool)</code> / <code>sorting_in_filter(bool)</code> / <code>sorting_links(bool)</code></td>
 <td>on</td>
 <td>Toggle sort UIs.</td>
 </tr>
 <tr>
-<td>‘filter_label_class` / `filter_input_class` / `filter_select_class` / `filter_item_wrapper_class`</td>
+<td><code>filter_label_class</code> / <code>filter_input_class</code> / <code>filter_select_class</code> / <code>filter_item_wrapper_class</code></td>
 <td>—</td>
 <td>CSS classes for filter form elements.</td>
 </tr>
@@ -213,9 +213,9 @@
 
 <p>Constructor <code>skip_*</code> kwargs: <code>skip_pagination</code>, <code>skip_filtering</code>, <code>skip_sorting</code>, <code>skip_sorting_in_filter</code>, <code>skip_sorting_links</code>, <code>skip_columns:</code>, <code>skip_row_intents:</code>, <code>skip_filters:</code>, <code>results_per_page:</code>, <code>default_sorting:</code>.</p>
 
-<h2 id="label-Customizing+rendering">Customizing rendering</h2>
+<h2 id="customizing-rendering">Customizing rendering</h2>
 
-<p><code>List</code> exposes named <code>content</code> blocks (<code>:data</code>, <code>:filter</code>, <code>:pagination</code>, <code>:sorting_links</code>, …) that you override — almost always once, in an app <code>BaseComponents::List</code>, to fit your UI framework, then inherited everywhere:</p>
+<p><code>List</code> exposes named <code>content</code> blocks (<code>:data</code>, <code>:filter</code>, <code>:pagination</code>, <code>:sorting_links</code>,…) that you override — almost always once, in an app <code>BaseComponents::List</code>, to fit your UI framework, then inherited everywhere:</p>
 
 <pre class="code ruby"><code class="ruby"><span class='kw'>module</span> <span class='const'>BaseComponents</span>
   <span class='kw'>class</span> <span class='const'>List</span> <span class='op'>&lt;</span> <span class='const'><span class='object_link'><a href="Compony.html" title="Compony (module)">Compony</a></span></span><span class='op'>::</span><span class='const'><span class='object_link'><a href="Compony/Components.html" title="Compony::Components (module)">Components</a></span></span><span class='op'>::</span><span class='const'><span class='object_link'><a href="Compony/Components/List.html" title="Compony::Components::List (class)">List</a></span></span>
@@ -243,7 +243,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Tue Jun 30 22:41:19 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.maintaining.html

@@ -60,64 +60,64 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Maintaining+Compony">Maintaining Compony</h1>
+<h1 id="maintaining-compony">Maintaining Compony</h1>
 
 <p>Conventions for contributors and AI assistants working <strong>on the gem itself</strong> (not apps using it). Keeps docs, gemspec and the rendered API reference from drifting.</p>
 
-<h2 id="label-Every+change">Every change</h2>
+<h2 id="every-change">Every change</h2>
 <ul><li>
-<p><strong>Behavior change → CHANGELOG.</strong> Add a bullet under the top <code># unreleased</code> heading in  <a href="/CHANGELOG_md.html">CHANGELOG.md</a>. If it breaks existing apps, add a <code>## Steps to take</code>  subsection with the migration (see prior entries for the format).</p>
+<p><strong>Behavior change → CHANGELOG.</strong> Add a bullet under the top <code># unreleased</code> heading in <a href="/CHANGELOG_md.html">CHANGELOG.md</a>. If it breaks existing apps, add a <code>## Steps to take</code> subsection with the migration (see prior entries for the format).</p>
 </li><li>
-<p><strong>New/renamed DSL method → docs.</strong> Update <a href="/doc/guide/dsl_reference_md.html">dsl_reference.md</a>  (keep the <code># DSL method</code> source marker) and add a YARD summary with  <code>@param</code>/<code>@return</code>/<code>@api</code> on the method.</p>
+<p><strong>New/renamed DSL method → docs.</strong> Update <a href="/doc/guide/dsl_reference_md.html">dsl_reference.md</a> (keep the <code># DSL method</code> source marker) and add a YARD summary with <code>@param</code>/<code>@return</code>/<code>@api</code> on the method.</p>
 </li><li>
-<p><strong>Comments only / docs only is fine to note as such</strong> in the CHANGELOG (“no behavior  change”).</p>
+<p><strong>Comments only / docs only is fine to note as such</strong> in the CHANGELOG (“no behavior change”).</p>
 </li></ul>
 
-<h2 id="label-Releasing">Releasing</h2>
+<h2 id="releasing">Releasing</h2>
 <ol><li>
-<p>Bump the version in <code>lib/compony/version.rb</code>. Loading the Rakefile rewrites <code>VERSION</code>  from it; <code>.edge</code> marks an unreleased prerelease.</p>
+<p>Bump the version in <code>lib/compony/version.rb</code>. Loading the Rakefile rewrites <code>VERSION</code> from it; <code>.edge</code> marks an unreleased prerelease.</p>
 </li><li>
 <p>Run <code>rake gemspec</code> — regenerates <code>compony.gemspec</code> (never hand-edit it; it says so).</p>
 </li><li>
-<p>Move the <code># unreleased</code> CHANGELOG block to a <code># X.Y.Z</code> heading; start a fresh  <code># unreleased</code>.</p>
+<p>Move the <code># unreleased</code> CHANGELOG block to a <code># X.Y.Z</code> heading; start a fresh <code># unreleased</code>.</p>
 </li><li>
-<p>Run <code>yard doc</code> and <strong>commit the regenerated <code>doc/*.html</code></strong> — the rendered API  reference is committed and shipped in the gem (<code>s.files</code>), so stale HTML ships  otherwise.</p>
+<p>Run <code>yard doc</code> and <strong>commit the regenerated <code>doc/*.html</code></strong> — the rendered API reference is committed and shipped in the gem (<code>s.files</code>), so stale HTML ships otherwise.</p>
 </li><li>
 <p><code>bundle exec rubocop</code> clean.</p>
 </li><li>
 <p>Tag / push / <code>gem build</code> per your release flow (<code>bundler/gem_tasks</code>).</p>
 </li></ol>
 
-<h2 id="label-Dependencies">Dependencies</h2>
+<h2 id="dependencies">Dependencies</h2>
 <ul><li>
-<p>Hard deps and their constraints live <strong>only</strong> in the <code>:gemspec</code> task in  href="/Rakefile"></a>. Change them there, run <code>rake gemspec</code>, and update the mirror  table in <a href="/doc/integrations_md.html">integrations.md</a> in the same commit.</p>
+<p>Hard deps and their constraints live <strong>only</strong> in the <code>:gemspec</code> task in <a href="/Rakefile"><code>Rakefile</code></a>. Change them there, run <code>rake gemspec</code>, and update the mirror table in <a href="/doc/integrations_md.html">integrations.md</a> in the same commit.</p>
 </li><li>
-<p>Keep the README’s stated Rails/Ruby support in sync with  <code>required_ruby_version</code> / the <code>rails</code> constraint — the gemspec is authoritative.</p>
+<p>Keep the README’s stated Rails/Ruby support in sync with <code>required_ruby_version</code> / the <code>rails</code> constraint — the gemspec is authoritative.</p>
 </li></ul>
 
-<h2 id="label-Documentation+rendering">Documentation rendering</h2>
+<h2 id="documentation-rendering">Documentation rendering</h2>
 <ul><li>
-<p><code>doc/*.html</code> is generated by YARD from <code>lib/</code> + the extra files listed in  href="/.yardopts"></a>.</p>
+<p><code>doc/*.html</code> is generated by YARD from <code>lib/</code> + the extra files listed in <a href="/.yardopts"><code>.yardopts</code></a>.</p>
 </li><li>
-<p><strong>Adding a guide page?</strong> Add its path to <code>.yardopts</code> (after the <code>-</code> separator) or it  will not appear in the rendered reference, then re-run <code>yard doc</code>.</p>
+<p><strong>Adding a guide page?</strong> Add its path to <code>.yardopts</code> (after the <code>-</code> separator) or it will not appear in the rendered reference, then re-run <code>yard doc</code>.</p>
 </li><li>
-<p>Markdown changes to already-listed guide pages still need a <code>yard doc</code> re-run + commit  to refresh the HTML.</p>
+<p>Markdown changes to already-listed guide pages still need a <code>yard doc</code> re-run + commit to refresh the HTML.</p>
 </li><li>
-<p><code>yard doc</code> logs <code>Cannot resolve link to … from text:</code> for guide-to-guide Markdown links  and inline <code>&lt;code&gt;</code> in the guide pages. This is <strong>expected and benign</strong> — YARD tries to  treat them as Ruby code-object links. The pages render correctly and the links work on  GitHub. Do not rewrite guide cross-links to silence YARD. (Genuine broken <code>{Xref}</code> in  Ruby <code>lib/</code> comments are worth fixing; guide-Markdown link warnings are not.)</p>
+<p><code>yard doc</code> logs <code>Cannot resolve link to … from text:</code> for guide-to-guide Markdown links and inline <code>&lt;code&gt;</code> in the guide pages. This is <strong>expected and benign</strong> — YARD tries to treat them as Ruby code-object links. The pages render correctly and the links work on GitHub. Do not rewrite guide cross-links to silence YARD. (Genuine broken <code>{Xref}</code> in Ruby <code>lib/</code> comments are worth fixing; guide-Markdown link warnings are not.)</p>
 </li></ul>
 
-<h2 id="label-Patterns+derived+from+real+apps">Patterns derived from real apps</h2>
+<h2 id="patterns-derived-from-real-apps">Patterns derived from real apps</h2>
 <ul><li>
-<p><a href="/doc/guide/patterns_md.html">patterns.md</a> / <a href="/doc/guide/cookbook_md.html">cookbook.md</a> are  <strong>fully anonymized</strong>: no app, business, author or domain-model names; neutral domain  (<code>Account</code>, <code>Order</code>, <code>LineItem</code>, <code>Document</code>); app-wrapper-only APIs excluded or  generalized (this is a public LGPL repo).</p>
+<p><a href="/doc/guide/patterns_md.html">patterns.md</a> / <a href="/doc/guide/cookbook_md.html">cookbook.md</a> are <strong>fully anonymized</strong>: no app, business, author or domain-model names; neutral domain (<code>Account</code>, <code>Order</code>, <code>LineItem</code>, <code>Document</code>); app-wrapper-only APIs excluded or generalized (this is a public LGPL repo).</p>
 </li><li>
-<p>Document the <strong>secure</strong> variant only. Never reproduce an insecure shape (e.g. a  capability token without expiry) even if that is what an app currently does — show the  hardened form and call out the requirement.</p>
+<p>Document the <strong>secure</strong> variant only. Never reproduce an insecure shape (e.g. a capability token without expiry) even if that is what an app currently does — show the hardened form and call out the requirement.</p>
 </li></ul>
 
 <p><a href="/README_md.html#guide--documentation">Guide index</a></p>
 </div></div>
 
       <div id="footer">
-  Generated on Tue Jun 30 22:41:20 2026 by
+  Generated on Tue Aug 18 14:36:35 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.model_fields.html

@@ -60,7 +60,7 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Model+fields">Model fields</h1>
+<h1 id="model-fields">Model fields</h1>
 
 <p>Compony fields are your models’ attributes that you wish to expose in your application’s UI. They are a central place to store important information about those attributes, accessible from everywhere and without the need for a database connection.</p>
 
@@ -111,7 +111,7 @@
 <span class='kw'>end</span>
 </code></pre>
 
-<h2 id="label-Implementing+your+own+fields">Implementing your own fields</h2>
+<h2 id="implementing-your-own-fields">Implementing your own fields</h2>
 
 <p>You can implement your own model fields. Make sure they are all within the same namespace and inherit at least from <code>Compony::ModelFields::Base</code>. To enable them, write an initializer that overwrites the array <code>Compony.model_field_namespaces</code>. Namespaces listed in the array are prioritized from first to last. If a field (e.g. <code>String</code>) exists in multiple declared namespaces, the first will be used. This allows you to overwrite Compony fields.</p>
 
@@ -127,7 +127,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Tue Jun 30 22:41:19 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.nesting.html

@@ -60,7 +60,7 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Nesting">Nesting</h1>
+<h1 id="nesting">Nesting</h1>
 
 <p>Components can be arbitrarily nested. This means that any component exposing content can instantiate an arbitrary number of sub-components that will be rendered as part of its own content. This results in a component tree. Sub-components are aware of the nesting and even of their position within the parent. The topmost component is called the <strong>root component</strong> and it’s the only component that must be standalone. If you instead render the topmost component from a custom view, there is conceptually no root component, but Compony has no way to detect this special case.</p>
 
@@ -123,7 +123,7 @@ The number 3 has the binary form 11.
 
 <p>However, this is static and no fun. We cannot use the HTTP GET parameter any more because all three <code>Binary</code> sub-components listen to the same parameter <code>number</code>. To fix this, we will need to scope the parameter using the <code>param_name</code> as explained in the next subsection.</p>
 
-<h2 id="label-Proper+parameter+naming+for+-28nested-29+components">Proper parameter naming for (nested) components</h2>
+<h2 id="proper-parameter-naming-for-nested-components">Proper parameter naming for (nested) components</h2>
 
 <p>As seen above, components can be arbitrarily nested, making it harder to identify which HTTP GET parameter in the request is intended for which component. To resolve this, Compony provides nesting-aware scoping of parameter names:</p>
 <ul><li>
@@ -198,7 +198,7 @@ The number 8 has the binary form 1000. Enter a number and press ENTER: [8]
 
 <p>Note that this example is completely stateless, as all the info is encoded in the URL.</p>
 
-<h2 id="label-Rendering+List+as+sub+comp+in+Show">Rendering <code>List</code> as sub comp in <code>Show</code></h2>
+<h2 id="rendering-list-as-sub-comp-in-show">Rendering <code>List</code> as sub comp in <code>Show</code></h2>
 
 <p>A pattern often used is the following:</p>
 
@@ -220,14 +220,14 @@ The number 8 has the binary form 1000. Enter a number and press ENTER: [8]
 </li><li>
 <p><code>render_sub_comp</code> is thus given an <code>ActiveRecord</code> collection of <code>Quote</code> models and it builts an <a href="/doc/guide/intents_md.html">Intent</a> to figure out that <code>Components::Quotes::List</code> is the component that will be instanciated, given the appropriate quotes, and rendered here.</p>
 </li><li>
-<p>We also give <code>:&quot;user_#{@data.id}_quotes&quot;</code> to the parameter <code>turbo_frame</code>, which causes <code>render_sub_comp</code> to place the sub comp inside a frame that is named something like <code>:user_1_quotes</code>. Since compony’s List component[/doc/guide/pre_built_components/list.md] contains search and filter forms, the turbo frame makes sure that anything entered there does not interfere with other parameters.</p>
+<p>We also give <code>:&quot;user_#{@data.id}_quotes&quot;</code> to the parameter <code>turbo_frame</code>, which causes <code>render_sub_comp</code> to place the sub comp inside a frame that is named something like <code>:user_1_quotes</code>. Since compony’s <a href="/doc/guide/pre_built_components/list_md.html">pre-built List component</a> contains search and filter forms, the turbo frame makes sure that anything entered there does not interfere with other parameters.</p>
 </li></ul>
 
 <p><a href="/README_md.html#guide--documentation">Guide index</a></p>
 </div></div>
 
       <div id="footer">
-  Generated on Tue Jun 30 22:41:18 2026 by
+  Generated on Tue Aug 18 14:36:33 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.new.html

@@ -63,11 +63,11 @@
 <p><a href="/doc/guide/pre_built_components_md.html">List of pre-built components</a></p>
 </li></ul>
 
-<h1 id="label-Pre-built+components-3A+New">Pre-built components: New</h1>
+<h1 id="pre-built-components-new">Pre-built components: New</h1>
 
 <p>This component is the Compony equivalent to a typical Rails controller’s <code>new</code> and <code>create</code> actions.</p>
 
-<p><code>Compony::Components::New</code> is a resourceful standalone component based on href="./with_form_md.html"></a> that listens to two verbs:</p>
+<p><code>Compony::Components::New</code> is a resourceful standalone component based on <a href="./with_form_md.html"><code>WithForm</code></a> that listens to two verbs:</p>
 <ul><li>
 <p>GET will cause the New component to create a fresh instance of its <code>data_class</code> and render the form.</p>
 </li><li>
@@ -99,7 +99,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Tue Jun 30 22:41:19 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.ownership.html

@@ -60,7 +60,7 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Ownership">Ownership</h1>
+<h1 id="ownership">Ownership</h1>
 
 <p>Ownership is a concept that captures the nature of data to be presented by Compony. It means that an object only makes sense within the context of another that it belongs to. Owned objects have therefore no index component, because they don’t have meaning on their own. For instance:</p>
 <ul><li>
@@ -88,7 +88,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Tue Jun 30 22:41:19 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>